F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #78-0001

[Back to F-16 Aircraft Database menu | Missing Photos | Hall of Fame]

F-16 Aircraft Profile

Aircraft: 78-0001
LM Aero T/V 61-7
Plant General Dynamics
Local C/N
Delivered USAF 78001
F-16A Block 1
Current USAF 78001
F-16A Block 1
Status [pre]

⇦ Copy-paste this code to link this airframe from our forum

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
18 Aug 1978 [act] 78001 F-16A Block 1
06 Sep 1978 [act] 80001 F-16A Block 1
First USAF F-16
This F-16 was the first to roll off the General Dynamics production line at Fort Worth, TX. It was delivered to the USAF in August of 1978 and thus became the very first production F-16 to be delivered worldwide. Initial deliveries went to the 388th TFW at Hill AFB, where initial pilot training on the type was performed.
Unknown [act] 78001 USAF 6516 TS 'ED' F-16A Block 1
Mar 1979 [act] 78001 USAF 34 TFS 'HL' F-16A Block 1
Unknown [msh] 78001 USAF 34 TFS 'HL' F-16A Block 1
Suffered a mishap on landing. The nose gear would not come down. The pilot tried everything to get it down, no luck. It was decided he would land on the runway and keep his nose up as long as he could. There was some concern the external wing tanks would drag so of course the crash trucks were there in case of fire. The pilot brought the plane in very slowly and landed on the mains, kept the nose up and almost came to a stop before the nose dropped. The radome was of course scraped up, the ring around the intake and the lower tacan antenna was gone. The wing tanks were about 5-6 inches from the ground. It was found out the seals in the nose gear were almost totally deteriorated. It was the original nose gear from the factory. Everything that was damaged was replaced and the plane was flying three days later. Anyone who knows the exact date, please let us know.

Update: A visitor wonders if this was the mishap involving pilot Dick Hoover who could not get the nose gear down at a Red Flag exercise, but also was not sure about the exact date.

Unknown [act] 78001 USAF 34 TFS 'HL' F-16A Block 1
Unknown [act] 78001 USAF 57 FWW 'HL' F-16A Block 1
Detachment 16 at Nellis AFB.
Jul 1983 [act] 78001 USAF 310 TFTS 'LF' F-16A Block 1
Nov 1989 [act] 78001 USAF 159 FIS F-16A Block 1
No unit markings
May 1990 [act] 78001 USAF 134 FIS F-16A Block 1
Jun 1990 [act] 78001 USAF 107 TFS 'MI' F-16A Block 1
Oct 1991 [pre] 78001 F-16A Block 1
On a pedestal in Langley's Memorial Park, Virginia

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.

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]

Errors and Omissions

Dec 31, 2019 - 03:50 PM
78-0001's landing with nose gear retracted

In Spring 1981, I went through the TX course taught by the 34th TFS. On 19 Jun, my logbook records that our four-ship had to divert to SLC for a few hours because the runway at Hill was closed for an unextended nose gear in the pattern. I recall that it was flown by a 34th IP, Capt. Ed Kosiba. One week before, Ed was my instructor on an ACM flight when I had to land 001 at Michael AAF (Dugway) after the aircraft battery failed. Thus 001 was on the schedule and why I believe that it was the tail that Ed was flying on 19 June. I enjoy seeing 001 every couple of weeks when I visit Langley.

Best regards,

Mark "Martin" Baker, 429th TFS

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.