F-16 Reference

F-16 Aircraft Database

Airframe Details for F-16 #90-0778

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



F-16 Aircraft Profile

Aircraft: 90-0778
LM Aero T/V 1D-56
Plant General Dynamics
Local C/N
Delivered USAF 90778
F-16D Block 42H
Current USAF 90778
F-16D Block 42H
Status [act]
Still has LTC North's name on the front seat. Also has Col. Bud Mahurin's name on the back seat with current DCC and ADCC on the right side.


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

Aircraft History

Date Status Local S/N Airforce/Unit Version Name Info
30 Jun 1991 [act] 90778 F-16D Block 42H
19 Jul 1991 [act] 90778 USAF 19 TFS 'SW' F-16D Block 42H
01 Oct 1991 [act] 90778 USAF 19 FS 'SW' F-16D Block 42H
27 Dec 1992 [act] 90778 USAF 19 FS 'SW' F-16D Block 42H
Deployment: Southern Watch

Mar 1993 [act] 90778 USAF 33 FS 'SW' F-16D Block 42H
Special characteristics:
  • Mission Marks
MiG-25 Killer
The only F-16 to shoot down a MiG-25. The MiG-25 kill marking was placed on the left side just below the canopy frame to mark that kill of December 27, 1992. At the time of the kill the aircraft was part of the 19th FS but on loan to the 33rd FS. Gary North, the commander of the 33rd FS and the pilot on that day had the authority to have the aircraft transfered to the 33rd FS after returning from the deployment. Crew Chief Roy Murray launched the aircraft that day: "On 27 Dec 1992 I launched "Benji 41" for a combat mission from Dhahran, Saudi Arabia. The only reason for it flying the combat mission (4 Hours) that day was to take flying hours off it so it could go in for a phase inspection. Most of its flight time during Operation Southern Watch was (FAM) rides for in coming pilots and VIP's, being the only D model. The canopy was so bad that Lt. Col North (at that time) stated "it was like landing with a paper bag on your head. HA! The family bus still got the job done that day. I also remember a reporter asking Lt. Col North why he did not use the cheaper missile, his come back was great; he stated if you were in a fight and had a knife and a gun, which one would you use. We painted the star and a blue tail on it while it was in phase, because it was on loan from the 19th FS at the time, then it became a 33rd FS aircraft. I stayed as the Crew Chief of 778 when we returned to Shaw, AFB and then transferred out with it to Luke AFB, AZ. I took my retirement flight in 90-0778 and launched Gen. North one more time when he came through Luke. I do miss those days!
Oct 1993 [act] 90778 USAF 63 FS 'LF' F-16D Block 42H
Special characteristics:
  • Mission Marks
MiG-25 kill marking was retained with the 63rd FS.
Mar 2009 [act] 90778 USAF 310 FS 'LF' F-16D Block 42H
Still wears the MiG-25 kill marking.
Jun 2022 [act] 90778 USAF 310 FS 'LF' F-16D Block 42H
Still wears the MiG-25 kill marking. New desert brown color scheme.
Jul 2022 [act] 90778 USAF 309 FS 'LF' F-16D Block 42H
Still wears the MiG-25 kill marking. New desert brown color scheme.
10 Jul 2023 [act] 90778 USAF 8 FS 'LF' F-16D Block 42H
Still wears the MiG-25 kill marking. New desert brown color scheme.

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




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.