F-16 Reference
F-16 Reference
F-16 Community
Multimedia
F-16 News
5th Gen Fighters
F-35 Lightning II
F-22A Raptor
Other
|
Aircraft Profile
| USAF FY/N: 78-0007 |
|
|
LM Aero T/V |
61-13 |
| Plant |
General Dynamics |
| Local C/N |
|
| Delivered |
USAF 78007
F-16A Block 1 |
| Current |
USAF AAFG0234
F-16A Block 1 |
| Status |
[sto] |
|
First aircraft to be produced on the assembly line. All prior aircraft to this were hand built.
|
|
|
Copy-paste this code to link this airframe from the F-16.net forum
Aircraft History
| Date |
Status |
Local S/N |
Airforce/Unit |
Version |
Name |
Info |
| 11 May 1979 |
[act] |
78007 |
|
F-16A Block 1 |
|
|
| 12 May 1979 |
[act] |
78007 |
388 TFW 'HL' |
F-16A Block 1 |
|
|
| Apr 1983 |
[act] |
78007 |
310 TFTS 'LF' |
F-16A Block 1 |
|
|
| Oct 1992 |
[act] |
78007 |
416 TS 'ED' |
F-16A Block 1 |
|
|
|
|
| 27 Sep 1994 |
[sto] |
AAFG0234 |
AMARC 'ED' |
F-16A Block 1 |
|
|
|
|
Crew Chief Comments
Create your own Crew Chief Profile
If you crewed this jet and want to leave a comment, you can create your own profile in our Crew Chief Profiles section.
|
|
|
Crew Chief Profile
|
|
310th Fighter Squadron "Tophats"
, 1989 - 1989
|
|
|
Luke AFB it was a quick assignment
|
Abbreviations and symbols:
| [act] |
Active |
[msh] |
Involved in Mishap |
[sto] |
Stored (e.g. at AMARC) |
| [cld] |
Cancelled order |
[o/o] |
On Order |
T/V |
LM Aero Type/Version (Construction) number |
| [emb] |
Embargoed |
[pre] |
Preserved (museum, gateguard) |
[w/o] |
Write-off |
| [i/a] |
Instructional Airframe |
[scr] |
Scrapped |
 |
Photo Available |
Errors and Omissions
Jun 13, 2008 - 11:37 PM
|
My Dad
JJ Cummins, who's my dad, was the first to have his name etched on this aircraft. I remember it distinctly due to it having the "007" on the tail. I'll forward this link along to him to show him what happened to his baby. CPT Jayson Cummins US Army
|
Errors and omissions in the above text can be added here. Please 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.
|
|
|