F-16 Reference

F-16 Aircraft Database

United States Air Force F-16 Mission Marks

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

Found 200 aircraft, displaying 91-105 [Sorted by Unit and FY/n]
Local S/N AF/Unit Aircraft Name Marked Date Details
90818 USAF 22 FS 90-0818 Jan 2003 Details
90827 USAF 22 FS 90-0827 Oct 2000 Details
Wore several red mission markings.
90829 USAF 22 FS 90-0829 "22 FS" Jan 2003 Details
Wore mission markings.
90831 USAF 22 FS 90-0831 Jan 2003 Details
Wore 6 HARM mission markings.
90833 USAF 22 FS 90-0833 "22 FS" Unknown Details
Wore 10 red HARM mission markings. Only jet from Spangdahlem that deployed in 2003 that used its gun, shot up an Iraqi transport plane and airfield. After the war 4 HARMs and a six shooter was added to the markings.
90843 USAF 22 FS 90-0843 Jan 2003 Details
86262 USAF 23 FS 86-0262 17 Jan 1993 Details
Shot down a MiG-23 with an AMRAAM that was challenging the no fly zone over Iraq on January 17, 1993. This kill was the second kill using the AMRAAM missile.
91407 USAF 23 FS 91-0407 Unknown Details
Wore 10 blue HARM mission markings in 2003.
91408 USAF 23 FS 91-0408 06 Sep 1995 Details
Aircraft fired the first HARM in combat. A kill marking was added just above the gun muzzle.
91409 USAF 23 FS 91-0409 Unknown Details
13 HARM mission markings in 2003.
91418 USAF 23 FS 91-0418 Unknown Details
6 HARM mission markings in 2003.
92915 USAF 23 FS 92-3915 Unknown Details
Wore 8 mission markings of HARMS. This aircraft may also have worn a kill marking which was removed as credit wasn't given. Many crew feel that the aircraft should have been credited with a kill.
92918 USAF 23 FS 92-3918 24 May 1995 Details
Wore 3 radar/Harm kill markings.
85552 USAF 23 TFS 85-1552 "52 TFW" Nov 1990 Details
90778 USAF 33 FS 90-0778 Mar 1993 Details
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!

First Previous 1234567891011121314 Next Last

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.