4 members
182nd Fighter Squadron / 182ND
-
Security -
Exploration
History
World War II
Established in mid-1943 as a P-47 Thunderbolt fighter squadron, trained under I Fighter Command on Long Island and Massachusetts. Moved to England, arriving in January 1944. Began operations with IX Fighter Command on 14 March and flew a fighter sweep over the English Channel coast of France. Made strafing and bombing attacks on airfields, rail and highway bridges, trains, vehicles, flak positions, and V-weapon sites to help prepare for the invasion of France.
Supported the landings in Normandy early in June 1944 and began operations from the Continent later the same month. Aided in the taking of Cherbourg, participated in the air operations that prepared the way for the Allied breakthrough at St Lo on 25 July, and supported ground forces during their drive across France.
Continued to support ground forces, participated in the assault against the Siegfried Line, and took part in the Battle of the Bulge (December 1944 – January 1945) by attacking rail lines and trains, marshalling yards, roads and vehicles, armored columns, and gun positions. Operated with the Allied forces that pushed across the Rhine and into Germany.
After V-E Day, served with the army of occupation, being assigned to United States Air Forces in Europe. Inactivated in Germany on 20 August 1946.
Texas Air National Guard
The wartime 396th Fighter Squadron was re-designated as the 182d Fighter Squadron, and was allotted to the Texas Air National Guard, on 24 May 1946. It was organized at the Brooks Army Airfield and was extended federal recognition on 27 January 1947 by the National Guard Bureau. The 182d Fighter Squadron was bestowed the lineage, history, honors, and colors of the 396th Fighter Squadron. The squadron was assigned to the Texas Air National Guard 136th Fighter Group and was equipped with F-51D Mustangs.
The mission of the squadron was the air defense of Texas. During the postwar years, the 182d the 111th primarily trained the Hill Country and west Texas; the 181st Fighter Squadron, based at Love Field, Dallas, covered the north Texas, and the 111th Fighter Squadron, based at Houston Municipal Airport, covered east and southeast Texas to the Mexican Border.
Korean War Activation
As a result of the Korean War, the Texas Air National Guard was federalized and placed on active-duty status on 10 October 1950, being assigned to Ninth Air Force, Tactical Air Command (TAC). TAC ordered the 136th Fighter Group to Langley Air Force Base, Virginia, where the unit was re-designated to a Fighter-Bomber unit, and its status was changed to a Wing. At Langley, the 136th Fighter-Bomber Wing consisted of the following units:
111th Fighter-Bomber Squadron
182d Fighter-Bomber Squadron
154th Fighter-Bomber Squadron (Arkansas ANG).
136th FBW F-84E Thunderjet at Taegu Air Force Base (K-2), South Korea
At Langley AFB, the 136th trained with their F-51D Mustangs. Unfortunately losing two 111th FBS pilots in a training accident on 15 December. A third pilot was killed on 27 January 1951 in another accident. In February 1951, the aged F-51Ds that the unit had been flying since its activation in 1947 were replaced by F-84E Thunderjets, and the squadron began transition training on the jet fighter-bomber. Most of the training took place at Langley, although some pilots were sent to Shaw AFB, South Carolina. Maintenance crews, all new to jet aircraft, were trained at Langley and engine specialists were sent to the Allison plant in Indianapolis. Assigned to the Arkansas ANG 154th FBS at the time was a Navy exchange pilot, future NASA astronaut Lieutenant Walter Schirra (who happened to be the only pilot assigned to the 136th at the time who was a qualified jet pilot).
U.S. Air Force Captain John McMahn and Sergeant White of the 182nd Fighter-Bomber Squadron, Texas Air National Guard, close out flight records at Taegu Air Base, South Korea, following their Republic F-84E-15-RE Thunderjet (s/n 49-2360, nicknamed “Miss Jacque II”) becoming the first such aircraft to complete 1,000 flying hours, 1952. Note the mission markers.
In May 1951, less than seven months later, the wing was deployed to Japan, being attached to Far East Air Force and stationed at Itazuke Air Force Base, the first echelon of the 136th arriving on 18 May. The 136th replaced the Strategic Air Command 27th Fighter-Escort Wing, which had deployed to Far East Air Force in the early days of the Korean War. At Itazuke, the squadrons took over the F-84Es of the 27th FEW, which remained in place, its aircraft being reassigned from SAC to Far East Air Force inventory records. On 2 June, the final elements of the 136th arrived in Japan, the national guardsmen officially relieved the 27th Fighter Bomber Wing and the SAC airmen departed for the United States. The 136th was the first Air National Guard wing in history to enter combat.
From Japan the wing engaged in combat operations over South Korea, however flying in the North Pacific area was a challenge to the wing, losing seven F-84Es in non-combat operations and three in combat. On 26 June, in one of the largest air-to-air battles in Korea, two 182d FBS pilots, Captain Harry Underwood and 1st LT Arthur Olighter shot down an enemy MiG-15 that broke though an F-86 Sabre escort of four B-29s. Two other 111th FBS pilots, 1st Lt John Morse and John Marlins scored probables in the same encounter. These were the first combat victories by Air National Guard pilots. On 3 July the 136th sent their aircraft to North Korea, attacking FLAK batteries in downtown Pyongyang while other aircraft attacked North Korean airfields.
However, the short-legged F-84 had limited combat time over Korea, therefore on 16 November 1951 the wing moved to Taegu Air Force Base (K-2) in South Korea for its combat operations. In 1952, the 136th was re-equipped with the F-84G Thunderjet, designed for tactical close air support of ground forces.
During its time in combat, the 136th flew 15,515 combat sorties; was credited with 4 enemy aircraft destroyed; 7 probables and 72 others damaged. It was the first ANG unit to down a MiG-15; it dropped 23,749 (7,120 tons) of bombs and expended over 3 million rounds of .50 caliber ammunition; being awarded Five Korean Campaign Ribbons. The 136th Fighter-Bomber Wing was released from active duty and returned to the United States on 10 July 1952
Air Defense Command
182d F-86L Sabre Interceptors, 1959
With the 182d’s return from the Korean War, the squadron was re-equipped with the Very Long Range (VLR) F-51H Mustang, which had been developed to escort B-29 Superfortress bombers in the Pacific Theater from the Mariana Islands to the Japanese Home Islands. The F-51H would allow the squadron to intercept any unidentified aircraft over any part of Texas. The squadron became part of Air Defense Command (ADC) and resumed its postwar mission of Texas air defense.
It was not until August 1956 that the 182d received first-generation F-80C Shooting Star jets, replacing some of the last F-51H Mustangs in the USAF inventory. In 1957, the squadron was selected by the Air Defense Command to man a runway alert program on full 24-hour basis – with armed jet fighters ready to “scramble” at a moment’s notice. This event brought the wing into the daily combat operational program of the USAF, placing us on “the end of the runway” alongside regular USAF-Air Defense Fighter Squadrons. The obsolescent F-80 day fighters were upgraded to the all-weather/day/night F-86D Sabre Interceptor by the end of the year. In June 1959 the squadron traded their F-86Ds for the upgraded F-86L Sabre Interceptor with uprated afterburning engines and new electronics.
182d Fighter Interceptor Squadron – Convair F-102A 57-839
In July 1960 the unit became one of the first to transition to the F-102A Delta Dagger Mach-2 all-weather interceptor and began a 24-hour alert to guard the Texas Gulf coast. The 182d enjoyed the distinction of being the first F-102 “Deuce” squadron in the Air National Guard.
When flight operations ended at Brooks AFB in October 1960, the squadron was moved to nearby Kelly Air Force Base, beginning operations on 1 November 1960. In August 1961, as part of an Air Defense Command re-organization, the 182d Fighter Interceptor Squadron’s assignment to 136th Air Defense Wing was terminated with 136th being transferred to Tactical Air Command. As a result, the 182d was authorized to expand to a group level, and the 149th Fighter-Interceptor Group was established by the National Guard Bureau. The 182d Fighter Interceptor Squadron became the group’s flying squadron. Other squadrons assigned into the group were the 149th Headquarters, 149th Material Squadron (Maintenance), 149th Combat Support Squadron, and the 149th USAF Dispensary. The 149th was directly assigned to the Texas Air National Guard, being operationally gained by the Air Defense Command 33d Air Division.
As with many other ANG squadrons, the 182d temporally operated two TF-102 twin-seat trainers for ANG F-102 pilots while remaining on runway alert status. Also, the squadron operated T-33A Shooting Star jet trainers and a Convair VT-29 transport for courier duties.
Tactical Air Support
The famous “triple null” F-100D 56-3000, while assigned to the 182d TFS in the early 1970s.
In 1968, the Air National Guard began to retire its F-102s and the 182d was ordered to send their aircraft to Davis-Monthan AFB for storage at AMARC. In July, as part of the drawdown of continental fighter air defense, the 149th FIG was transferred from Aerospace Defense Command to Tactical Air Command (TAC), with the Group and 182d being re-designated as a Tactical Fighter Group and Squadron.
As an interim measure, the 182d Tactical Fighter Squadron was re-equipped with obsolescent F-84F Thunderjets by TAC. The squadron was the second-to-last ANG squadron to fly the F-84F. During the summer of 1971 the 182d began to receive F-100D/F Super Sabre tactical fighter bombers. The 182d was one of the first ANG squadrons to receive the Super Sabre, as most were being operated in South Vietnam at the time. The F-100s received by the squadron were aircraft being withdrawn from the 20th Tactical Fighter Wing at RAF Wethersfield and the 48th TFW at RAF Lakenheath, England.
RAF Wethersfield was being closed for flight operations and the 20th TFW being re-equipped with the new General Dynamics F-111 at their new base, RAF Upper Heyford. The 48th TFW – a permanent resident at RAF Lakenheath after moving aircraft and personnel from Chaumont AB in France – was also preparing for the arrival of the F-111, but had to initially convert to F-4D Phantom IIs before their ultimate F-111 version – the F-111F – came available during 1977.
The Super Sabre was dedicated fighter-bomber, with no concession being made to a secondary air-superiority role and the squadron trained in using the fighter for ground support. Beginning in 1975, the 182d began a NATO commitment, with squadron aircraft and personnel deploying to the United States Air Forces in Europe (USAFE) for Autumn Forge/Cold Fire/Reforger exercises.
By 1979, the Super Sabres were being retired, and were replaced by McDonnell F-4C Phantom IIs, largely Vietnam War veteran aircraft, that were made available to the Air National Guard. With the Phantom, the 182d continued their tactical fighter mission with the more capable aircraft. The squadron also continued its NATO deployments, exercising at USAFE bases in West Germany, England, the Netherlands and Denmark.
182d Tactical Fighter Squadron – McDonnell F-4C-19-MC Phantom 63-7569.
In 1986, the Phantoms were reaching the end of the operational service, and they were replaced by the F-16A Fighting Falcon. The F-16s were transferred from the 347th Tactical Fighter Wing, Moody AFB, Georgia. Initially the squadron began to receive Block 15 single-seat F-16As, and a few twin-seat F-16Bs.
The Block 15 was the major production model of the F-16A.
Higher-performance Block 25 F-16C/D aircraft replaced the standard fighter-bomber Block 15 A/B model aircraft in 1996. Although similar in appearance to the earlier models, the Block 25 aircraft were a considerable advancement with the Westinghouse AN/APG-68(V) multi-mode radar with better range, sharper resolution, and expanded operating modes. The planar array in the nose provides numerous air-to-air modes, including range-while-search, uplook and velocity search, single target track, raid cluster resolution, and track-while-scan for up to 10 targets. The radar was capable of handling the guidance of the AGM-65 Maverick air-to-surface missile. Upgraded engines made the aircraft capable of Mach-2 performance.
In 1997, the squadron deployed aircraft and personnel to Ahmed Al Jaber Air Base, Kuwait, in support of Operation Southern Watch.
However, the Block 25 aircraft were all powered by the Pratt & Whitney F100-PW-200 turbofan, which were prone to engine stalls. In 1998, the squadron received Block 30 aircraft, with wider intakes and the General Electric F-110 engine. However, by the mid-1990s and with the end of the Cold War, there appeared to be no longer any threat to America’s homeland from bombers or cruise missiles.
2000s
Crew chiefs recover their F-16 after it returned to Hickam AFB, Hawaii from an air to air mission on September 8th, 2006 during Exercise Sentry Aloha.
In 1999, the mission of the 149th Fighter Group was changed from Air Combat operations to becoming a Formal Training Unit (FTU) for Air National Guard F-16 pilots under Air Education and Training Command. The 182d provides combat training for active duty, Air National Guard, and Reserve F-16 pilots, including recent graduates from USAF Undergraduate Pilot Training making them combat ready upon graduation of a 9 month course. Almost all instructor pilots within the unit are former active duty F-16 pilots.
Although the squadron is not officially a combat unit, after the 9/11 attacks in 2001 and 2002, the squadron flew Operation Noble Eagle air defense missions in the United States in support of USNORTHCOM and the U.S. Department of Homeland Security. It also deploys to other bases, flying Dissimilar air combat training missions against active-duty, reserve and ANG units.
In its 2005 BRAC Recommendations, DoD recommended to realign the 178th Fighter Wing, Ohio Air National Guard to an MQ-1 Predator ISR mission and transfer six additional Block 30 F-16 aircraft to the 182d Fighter Squadron. DoD claimed that its recommendation was made because Lackland (Kelly Annex) (47) had higher military value than Springfield-Beckley AGB (128). This recommendation also would optimize the squadron size of the 182d, the only ANG F-16 Flying Training Unit.
The squadron’s Block 30 aircraft, manufactured between 1987 and 1989 were at the end of their service life and in 2016 the United States Air Force made the decision to disband the unit.
Kilrathi War
The unit did not see any further action till it was reactivated in 2629 following that attack on the TCS Iason by Kilrathi forces. In 2654 after being reactivated the unit quickly became a bastard unit of Unified Space Command serving on many ships with distinction in the Vega, Enigma Campaign, and Gauntlet Campaigns. The unit was decorated several times for its service at the Battle of Battle of McAuliffe, Battle of Repleetah, and Battle of Earth.
A New Chapter
In 2669 after the Kilrathi war ended the Terran Confederation slowly was replaced by the United Nations of Earth, which later became the United Empire of Earth, the unit was set to be disbanded yet again. Several officers of the unit took it upon themselves to take the now defunct unit and carry on its name as a private corporation that offers the galaxies best in security and exploration services.
Lineage
Constituted 396th Fighter Squadron on 24 May 1943.
Activated on 1 June 1943
Inactivated on 20 August 1946
Re-designated 182d Fighter Squadron and allotted to Texas Air National Guard on 21 August 1946
Extended federal recognition on 27 January 1947
Federalized and ordered to active service on: 10 October 1950
Re-designated: 182d Fighter-Bomber Squadron, 19 April 1951
Released from active duty and returned to Texas state control, 10 July 1952
Re-designated: 182d Fighter-Bomber Squadron, 10 July 1952
Re-designated: 182d Fighter Interceptor Squadron, 1 July 1955
Re-designated: 182d Tactical Fighter Squadron, 1 July 1968
Re-designated: 182d Fighter Squadron, 16 March 1992
Components designated as: 182d Expeditionary Fighter Squadron when deployed as part of an Air and Space Expeditionary unit after June 1996.
Deactivated : 2016
Reactivated: 2629
Left Military Service and Became Private Corperation: 2669
Assignments
368th Fighter Group, 1 Jun 1943 – 20 Aug 1946
136th Fighter Group, 27 January 1947
136th Fighter-Interceptor Group, 20 July 1952
136th Fighter-Bomber Group, 1 January 1953
136th Air Defense Group, 1 July 1957
149th Fighter-Interceptor Group, 1 August 1961
149th Tactical Fighter Group, 1 July 1968
149th Fighter Group, 16 March 1992
149th Operations Group, 1 October 1995
Terran Confederation Unified Space Command 2629
Manifesto
The 182nd Fighter Squadron is a unit of dedicated operators that dominate every form of multifaceted security and exploration missions. Constantly achieving their mission objectives by the use of training, preparation, teamwork, professionalism, and dedication to excellence.
Charter
We have a set of rules that must be followed, since discipline is a key part of our unit.
• Respect other units at all times
• Respect and obey all orders given out by a superior officer
• Anyone caught cheating, hacking, or any other thing like this will be dealt with quickly by the Command Group.
• Rules of Engagement
Also called the Rules of Engagement, or RoE for short, are the preferred method of combat and must be obeyed at all times. The RoE is there to protect you and the unit and breach of the RoE must be reported to the Command Group IMMEDIATELY.
• Player Conduct
We are all here to have fun. This is a game after all, and it should be treated as such. However, the Unit realizes that times do occur when players do not act appropriately. With any game, this game brings emotion, and emotion often times leads to rash acts. Though they are understanding of it, the Unit does frown upon these types of actions. Repeated offenses will resulted in people being banned. The Unit expects that all players abide by the codes of conduct presented here. Should they not follow these guidelines, they could be subject to dismissal from the Unit.
• Reporting Problem Players
Should a situation arise whereby a player would be subject to dismissal from the Unit, there is a procedure, which must be followed by all, in order for the problem to be taken care of. The Unit would like to stress that not all offenses are punishable by banning. Only severe instances will result in such actions, along with repeat offenses. We realize that people do things when they are mad that they later regret, and often times are satisfied with a simple public apology. However there are times when a player should be removed, and the following is the procedure that should be followed. Report the problem, along with any pertinent proof and or information that you have to the Commander of the unit. The High Command will then review the proof and information provided to them, and work the investigation accordingly. They will report their findings to the Commander, who will then decide on what action, if any should be taken.
• Acceptable Proof
The Administration must be very picky of what types of proof can be accepted as accusations of cheating, or other offenses. The following are the only types of proof accepted.
• Official Chat Log Files
• Screen Shots from games
• Official Game Logs (If Any)
• Testimonial from witnesses (Note this is only in certain instances)
These types of proof are the only types that will be accepted in any circumstance. You must have one or more qualifying types of proof in order to present a case to the Council.
Official Unit of Conduct
• Cheating
At no time shall any player in any game cheat. Any player found cheating intentionally would be automatically banned for life.
• Spying
Spying is completely dishonorable and shall not be done by any member of the unit.
• Cursing & Offensive Remarks
Remarks of a racial nature will not be tolerated. As far as cursing goes, everyone curses, and the Khan realizes that. However it is the context in which the curse is used which often times causes conflicts. Should any conflict arise in which cursing is involved, the Khan will rule on all context involved and act accordingly. In essence, if you curse in a manner that is not direct AT anyone, often times you wont cause much of a problem.
• Gloating
Ok let’s face it, people win, they like to celebrate their win. However like all things, there is a line that is present that if it is crossed, often times lead to arguments because one person feels that the winners are gloating over them. If you are the winner in a battle, or a match, just remember that at that particular point in time the losing player’s pride is hurt, and they will react very harshly to rude comments made by you. A good winner simply says “good game” and exits, and celebrates with his comrades, and not in front of the other player. This is more of a courtesy rule than anything else, though you can get a nasty reputation for gloating.
• Whining & Pouting
So you lost, what’s the big deal? Keep in mind that this is only a game, and nothing more. This isn’t real life, and the only thing that’s hurt is your pride. Keep your chin up, and come back next game and put a real whooping down on someone. There’s no need to complain, and accuse, and whine, and pout. Star Commanders are urged to NOT deal with this, and expect that all players act as mature as possible.
• Cheating Accusations
Should you feel that someone is cheating, you must have proof. You must keep your thoughts to yourself. The Unit will not tolerate any public accusations of cheating. This can ruin the image of a player, and no matter if the player is found to have been cheating or not, he becomes someone who is always thought to have been a cheater. You are to follow procedure as stated above when reporting a cheater, should you have the proof.
• Attitudes & Egos
These simply will not be tolerated. We are all here to have fun, and people with attitudes and/or egos are just a waste of time. You’ll end up alone very quickly if you have this type of problem.
• Online Attacks
This is just plain rude, and the Unit hopes that no player participates in these types of actions. Any player found participating in these actions would be removed, so keep that in mind.
• Cheating and Hacking
The very nature of Combat Operations involves secrecy, and the efforts of the opposing side to uncover those secrets. That said: EXPECT to be spied upon, and trust NO ONE! Knowledge is power; so all manner of LEGAL spying is to be expected, including moles, and possibly even double agents.
As mentioned in the Code of Conduct however, confirmed incidents Hacking and other forms of illegal activities will result in banning from the Unit, as well as any other actions that are within the powers of the Unit to take. Confirmed incidents of Cheating by any manner presently known, and/or unknown, shall result in instant banning from the Unit, as well as any other actions that are within the powers of the Unit to take.
If a commanding officer (CO) deems the evidence of cheating and/or hacking worthy of consideration, he will bring the matter before the Command Group for consideration. If the Command Group deems the case worthy of being suspect, it will then decide on any action to be taken against the player. Commanders are to ensure that their Players are meeting all Play requirements
Cheating claims should have supporting evidence and WILL remain confidential. If a claim is made with no evidence, or if any pending claims are discussed in public, the CO, with the approval of the rest of the Command Group, may penalize the claimant’s rank in a manner to be decided by the Command Group. In other words, be discrete.
