DCA92MA049 · Mitsubishi MU-2B-60
Solar Sources Mitsubishi MU-2B-60 and Raf Flying Servies Piper PA-32-301 · Accident: midair collision en route
Event
- NTSB case
- DCA92MA049
- 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
- Accident
- 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
- API-reported fatalities
- 6 · all aircraft and ground
- Ground fatalities
- 0
- 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
- General aviation
- 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 · Mitsubishi MU-2B-60
- Aircraft type
- Mitsubishi MU-2
- 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
- N74FB
- Operator
- Solar Sources
- Onboard fatalities
- Unknown
- Route
- From not recordedTo COL · Columbus, OH
- 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
- Part 91: General Aviation
- 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
- En route · climb to cruise
- First occurrenceThe 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Aircraft 2 · Piper PA-32-301
- Aircraft type
- Piper PA-32
- 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
- N82419
- Operator
- Raf Flying Servies
- Onboard fatalities
- Unknown
- Route
- From Indianapolis, INTo not recorded
- 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
- Part 91: General Aviation
- 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
- En route · descent
- First occurrenceThe 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
- Midair collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PA-32, N82419, HAD BEEN RECEIVING ATC RADAR SERVICES EN ROUTE TO THE GREENWOOD MUNI ARPT. RADAR SERVICES WERE TERMINATED 3 MI FROM THE ARPT. THE MU-2, N74FB, HAD JUST TAKEN OFF FROM THE ARPT, AND HAD REPORTED TO ATC IN ANTICIPATION OF RECEIVING HIS IFR CLEARANCE. THE FLIGHT HAD NOT YET BEEN IDENTIFIED ON RADAR. THE TWO AIRPLANES COLLIDED APRX 2 MI FROM THE ARPT AT 2,100 FT MSL. THE COLLISION TOOK PLACE JUST OUTSIDE AND TO THE EAST OF THE INDIANAPOLIS AIRPORT RADAR SERVICE AREA (ARSA). THE MU-2 TRACK WAS 066 DEG, AND THE PA-32 TRACK WAS 174 DEG. THE PAX/PLT ON THE PA-32 TOOK CONTROL OF THE AIRPLANE & WAS ABLE TO MAKE A CONTROLLED LANDING. GUIDANCE FOR TRAFFIC PATTERN OPERATIONS & RECOMMENDED ARRIVAL AND DEPARTURE PROCEDURES IS FOUND IN THE AIRMAN'S INFORMATION MANUAL.
Probable cause
THE INHERENT LIMITATIONS OF THE SEE-AND-AVOID CONCEPT OF SEPARATION OF AIRCRAFT OPERATING UNDER VISUAL FLIGHT RULES THAT PRECLUDED THE PILOTS OF THE MU-2 AND THE PA-32 FROM RECOGNIZING A COLLISION HAZARD AND TAKING ACTIONS TO AVOID THE MIDAIR COLLISION. CONTRIBUTING TO THE CAUSE OF THE ACCIDENT WAS THE FAILURE OF THE MU-2 PILOT TO USE ALL THE AIR TRAFFIC CONTROL SERVICES AVAILABLE BY NOT ACTIVATING HIS INSTRUMENT FLIGHT RULES FLIGHT PLAN BEFORE TAKEOFF. ALSO CONTRIBUTING TO THE CAUSE OF THE ACCIDENT WAS THE FAILURE OF BOTH PILOTS TO FOLLOW RECOMMENDED TRAFFIC PATTERN PROCEDURES, AS RECOMMENDED IN THE AIRMAN'S INFORMATION MANUAL, FOR AIRPORT ARRIVALS AND DEPARTURES. (NTSB REPORT AAR-93/05)
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA92MA049
- Event ID
- 20001211X15679
- Case number
- DCA92MA049
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: a2f04b36574dfe80177261fbc46fdda98cd7b40567289d62e0d3c8a0fe22921f; retrieved 2026-09-21T00:57:12.820Z.