AM64
Well-Known Member
- Joined
- Feb 11, 2016
- Messages
- 28,555
- Likes
- 42,356
Not all carried the WW code. The 35th FW in particular was the original unit tasked with SEAD hence the WW tail code the unit (George AFB at the time) was allowed to adopt. The tail code followed the unit to Misawa during the major BRAC and realignment during the 90s.
There are/were other SEAD capable units in the USAF (53rd FW at Spangdahlem AB for example with tail code "SP") and, in reality, even more today. Most of the F-16CJ models are capable of performing that SEAD mission since they are installed with the proper avionics.
Tail codes are curious things in the USAF. Some are tied to a specific base, others are historically tied to the unit they were assigned. FF for example, (First Fighter) is tied to the 1st Fighter Wing and that's something they won't give up even if they move. Others (SP at Spangdahlem with the 52nd, EG at Eglin with the 33rd, etc) are tied to the location and if/when units move, they assume that tail code.
My brother flew F-106s and then F-15s in the 94th Fighter Squadron - 1st FW, so I knew that history and why they use the FF. You'd almost think the LN for Lakenheath would be Langley - but not. The history of AF units can be fascinating - like the F-15s at Lakenheath are the 493rd - which is the WW2 squadron my dad flew with; and the 75th that he flew with was one of the original Flying Tiger squadrons. Not sure when tail codes came back into being; I can't remember them in the 50s and 60s when I was growing up on AF bases.