F-16 Reference
F-16 Aircraft Database
Airframe Details for F-16 #93-0723
F-16 Aircraft Profile
Aircraft:
93-0723
|
||
LM Aero T/V | TA-22 | |
Plant | Lockheed - Fort Worth | |
Local C/N | ||
Delivered |
RoCAF
6622
F-16A Block 20 |
|
Current |
RoCAF
6622
F-16A Block 20 |
|
Status | [w/o] | |
|
⇦ Copy-paste this code to link this airframe from our forum
Aircraft History
Date | Status | Local S/N | Airforce/Unit | Version | Name | Info | ||
---|---|---|---|---|---|---|---|---|
Unknown | [act] | 6622 | F-16A Block 20 | |||||
|
||||||||
Aug 1999 | [act] | 6622 | RoCAF 21 TFS | F-16A Block 20 | ||||
Dec 2002 | [act] | 6622 | RoCAF 22 TFS | F-16A Block 20 | ||||
Mar 2004 | [act] | 6622 | RoCAF 23 TFS | F-16A Block 20 | ||||
01 Nov 2004 | [act] | 6622 | RoCAF 21 TFG | F-16A Block 20 | ||||
15 May 2013 | [msh] | 6622 | RoCAF 21 TFG | F-16A Block 20 | News Article | |||
|
||||||||
15 May 2013 | [w/o] | 6622 | RoCAF 21 TFG | F-16A Block 20 |
Crew Chief Comments
Create your own Crew Chief ProfileIf you crewed this jet and want to leave a comment, you can create your own profile in our Crew Chief Profiles section.
Abbreviations and symbols:
[act] | Active | [i/a] | Instructional Airframe | [sto] | Stored (e.g. at AMARG) |
[cld] | Cancelled Order | [msh] | Involved in Mishap | [w/o] | Write-off |
[con] | Converted | [o/o] | On Order | ||
[des] | Destroyed (drone) | [pre] | Preserved (museum, gateguard) | T/V | LM Aero Type/Version (Construction) number |
[emb] | Embargoed | [scr] | Scrapped | Photo Available |
Any aircraft or serials missing from this list? Did you see incorrect, incomplete, or
outdated data?
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]
Add your corrections at the bottom of this page or send them to us!
[Back to the F-16 Aircraft Database]
Errors and Omissions
Please use this form to add any list any error or omissions you find in the above text.
Note: your comments will be displayed immediately on this page. If you wish to send a private comment to the webmasters, please use the Contact Us link.