FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

OPS11IA499 · Boeing 737

18 Apr 2011 · Camp Springs, MD, United States

United States Air Force Boeing 737 and United States Air Force Boeing C17 A · Incident: near midair/TCAS alert/loss of separation on approach

Report a problem

Event

NTSB case
OPS11IA499
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Military
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Boeing 737

Aircraft type
Boeing 737
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
Unknown
Onboard fatalities
Unknown
Route
From UnknownTo Joint Base Andrews (ADW), Camp Springs, MD
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Armed Forces
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR final approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Near midair/TCAS alert/loss of separation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Boeing C17 A

Aircraft type
Boeing C17
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
Unknown
Onboard fatalities
Unknown
Route
From UnknownTo Joint Base Andrews (ADW), Camp Springs, MD
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Armed Forces
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · IFR final approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Near midair/TCAS alert/loss of separation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A Boeing 737 (B737) and a heavy Boeing C-17 were being provided radar vectors for instrument landing system approaches to the runway by a controller at the Potomac Terminal Radar Approach Control (TRACON) facility. The controller vectored the C-17 onto the base leg of the traffic pattern ahead of the B737 to join the localizer for the approach. At this point, the airplanes were separated by 4.45 miles on a converging course with a closure rate of 180 knots. The C-17 was subsequently vectored to join the localizer and cleared for the approach. The controller then issued a wake turbulence advisory to the B737 and informed the pilot he would be 4 miles in trail of the C-17. The pilot of the B737 acknowledged the advisory, but, at this point, the airplanes were 3.62 miles apart. The minimum required wake turbulence separation was 5 miles. Both airplanes were directed to contact the air traffic control tower local controller. As both airplanes reduced their speeds for landing during final approach, their separation was reduced to 2.81 miles. The minimum instrument flight rules separation was 3 miles. The local controller authorized the B737 to make "S" turns on final approach to increase separation; however, when the B737 was 2 miles from the landing threshold, the B737 pilot told the local controller, "it doesn't look like we're going to make this," since the C-17 was still conducting the landing roll on the runway. The B737 pilot was instructed to perform a go-around, entered a left downwind for the runway, and landed uneventfully.

The TRACON controller responsible for the wake turbulence operational error reported after the incident that he confused the minimum wake turbulence separation requirements for a B737 following a C-17 with the requirement for a B757 following a B757. The B757 requirement was 4 miles. The TRACON controller had been involved in 4 other operational errors in the 4 years preceding this incident.

Probable cause

The misapplication of wake turbulence and instrument flight rules (IFR) separation criteria by air traffic controllers.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS11IA499
Event ID
20110420X31215
Case number
OPS11IA499
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 52595480617248a0125749e115161de9fbc6e4189420cf53066e152cd13e7a32; retrieved 2026-09-13T18:18:24.134Z.