World War II Initial organization and training The
squadron was first established in March 1942 at
Gowen Field, Idaho, as the 367th Bombardment Squadron, one of the original four squadrons of the
306th Bombardment Group. In April, its personnel moved to
Wendover Field, Utah, where it began training with
Boeing B-17 Flying Fortress heavy bombers.
Combat in Europe The squadron settled into its combat station,
RAF Thurleigh, England, in early September. Although several bomber units arrived in England before the 367th, when these units left England to participate in
Operation Torch it became, along with its companion squadrons of the 306th Group, the oldest bombardment squadrons of
VIII Bomber Command. It few its first combat mission on 9 October 1942 against a steel factory near
Lille, France, but with poor results. This was the first mission on which VIII Bomber Command assembled a strike force of over 100 bombers. The squadron operated primarily against strategic targets, including the locomotive factory at Lille,
marshalling yards at
Rouen, France, and
Stuttgart, Germany. The squadron took part in the first strike into Germany by bombers of
Eighth Air Force on 27 January 1943 when it struck
U-boat yards at
Wilhelmshaven. It struck
shipbuilding yards at
Vegesack, ball bearing plants at
Schweinfurt, the aircraft factory at
Leipzig, Germany, and similar facilities. For this mission, the squadron was awarded the
Distinguished Unit Citation (DUC). The following month the squadron earned a second DUC for its performance during
Big Week, an intensive bombing campaign against the German aircraft industry. Despite adverse weather on 22 February that led supporting elements to abandon the mission the squadron and group effectively bombed the aircraft assembly plant at
Bernburg, Germany. In February 1946, the squadron moved to
Istres-Le Tubé Air Base, France, where it absorbed elements of the inactivating
92d and
384th Bombardment Groups, returning to Germany in July. The 367th supports the
Air Combat Command and the
Air Mobility Command by providing fact-based performance analysis, identifying root causes of performance deficiencies, and recommending possible solutions. Members of the squadron's analysis section travel to maintenance units across the Air Force to analyze performance deficiencies and identify training gaps. Once initial analysis is complete, design members interpret the collected data and apply ISD principles to create the framework. This framework is then passed along to the software development and graphics sections to create the designed framework. Finally, the near-finished products are scrutinized for technical accuracy, safety compliance, and overall quality by the evaluation section. Then the product is provided to a focus-group from the target audience for feedback. Once stamped with a
seal of approval, products are hosted on the internally-developed and maintained Griffin website for field level use. ==Lineage==