MIA93LA199 · Boeing E75
Boeing E75 and Cessna 150G · Accident: midair collision on approach
Event
- NTSB case
- MIA93LA199
- 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
- 0 · 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 · Boeing E75
- Aircraft type
- Boeing E75
- 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
- N43320
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lafayette Landings Airport (FD90)To Lafayette Landings Airport (FD90)
- 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
- Approach · VFR pattern final
- 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
- Substantial
Aircraft 2 · Cessna 150G
- Aircraft type
- Cessna 150
- 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
- N2660J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dehradun Jolly Grant Airport (DED)To Lafayette Landings Airport (FD90)
- 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
- Approach · VFR pattern final
- 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
- Substantial
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 AIRSTRIP OWNER HAD ADVISED THE PILOT OF A BOEING E75 (N43320) TO USE A RIGHT TRAFFIC PATTERN FOR LANDING DUE TO THE NUMBER OF AIRCRAFT INVOLVED IN A FLY-IN. AS THE E75 PILOT WAS IN A RIGHT PATTERN TO LAND, A CESSNA 150 (N2660J), WHICH WAS ARRIVING FROM ANOTHER AIRPORT, WAS IN A LEFT PATTERN FOR LANDING ON THE SAME RUNWAY. SUBSEQUENTLY, THE 2 AIRCRAFT CONVERGED ON FINAL APPROACH & COLLIDED. BOTH ACFT TOUCHED DOWN HARD & SUSTAINED SUBSTANTIAL DAMAGE; THE OCCUPANTS OF BOTH AIRCRAFT RECEIVED MINOR INJURIES. BOTH PILOTS WERE MONITORING THE SAME RADIO FREQUENCY OF A NEARBY AIRPORT, BUT NEITHER PILOT TRANSMITTED INTENTIONS FOR LANDING. INVESTIGATION REVEALED THAT JUST BEFORE THE COLLISION, THE CESSNA 150 WAS BELOW THE BOEING E75 AS THEY CONVERGED. ACCORDING TO THE AIRMAN'S INFORMATION MANUAL, ALL TURNS IN THE TRAFFIC PATTERN SHOULD HAVE BEEN MADE TO THE LEFT, WHILE APPROACHING TO LAND, UNLESS A TRAFFIC PATTERN INDICATOR INDICATED OTHERWISE. NEITHER A TRAFFIC PATTERN INDICATOR NOR A UNICOM RADIO WERE INSTALLED AT THE AIRSTRIP.
Probable cause
FAILURE OF BOTH PILOTS TO MAINTAIN ADEQUATE VISUAL LOOKOUT. FACTORS RELATED TO THE ACCIDENT WERE: THE CONFLICTING RIGHT TRAFFIC PATTERN PROCEDURES FOR LANDING THAT WERE BRIEFED TO THE BOEING E75 PILOT BY THE OWNER OF THE AIRSTRIP, AND FAILURE OF BOTH PILOTS TO TRANSMIT THEIR LANDING INTENTIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93LA199
- Event ID
- 20001211X13462
- Case number
- MIA93LA199
- 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: ec92060638c46d24b437c92a537696fa91240a0011e8b7ba5827e45387015743; retrieved 2026-09-21T22:47:57.522Z.