FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18FA194 · Piper PA34 200

17 Jul 2018 · Miami, FL, United States

Dean International Piper PA34 200 and Dean International Cessna 172 N · Accident: midair collision en route

Report a problem

Event

NTSB case
ERA18FA194
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
4 · all aircraft and ground
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
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 · Piper PA34 200

Aircraft type
Piper PA34
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
N16281
Onboard fatalities
Unknown
Route
From Miami Executive Airport (TMB), Miami, FLTo Miami Executive Airport (TMB), Miami, FL
Aircraft age
About 45 years (built 1973)
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 · cruise
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
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 · Cessna 172 N

Aircraft type
Cessna 172
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
N6428D
Onboard fatalities
Unknown
Route
From Immokalee Regional Airport (IMM), Immokalee, FLTo Miami Executive Airport (TMB), Miami, FL
Aircraft age
About 39 years (built 1979)
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 · cruise
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
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

  • Personnel issues › Psychological

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

NTSB narrative

A low-wing multiengine airplane departed the airport on an evaluation flight in the local training area with a commercial pilot candidate and designated pilot examiner onboard. The student pilot and a flight instructor onboard a high-wing airplane were returning to the same airport on a cross-country instructional flight. About 6 minutes after the low-wing airplane departed, the airplanes collided nearly straight-on about 1,500 ft mean sea level and 9 miles northwest of the airport. At the time, the low-wing airplane was clear of the Class D airspace and no longer communicating with air traffic control (ATC). One of the pilots in the high-wing airplane had contacted ATC just before the collision. The controller acknowledged the transmission and issued a traffic advisory, but no further communications were received. Neither airplane was equipped with a traffic information system, nor were they required to be.

An aircraft performance and cockpit visibility study revealed that both airplanes would have remained relatively small, slow-moving objects in each other's windows until about 12 seconds before the collision, and subsequently grown in size suddenly; however, it is likely that none of the pilots saw the other airplane given that radar data does not indicate that either airplane performed evasive maneuvers to avoid the collision No preimpact mechanical malfunctions were identified with either airplane. Toxicology testing identified low levels of delta-9-tetrahydrocannabinol (THC) and metabolites in the high-wing flight instructor's blood and urine. Their presence indicates that the instructor had used marijuana at some time before the accident, but it is unlikely that the psychoactive effects of THC remained or contributed to the accident.

Probable cause

The failure of both pilots in both airplanes to see and avoid the other airplane as they converged nearly head-on at the same altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18FA194
Event ID
20180717X43051
Case number
ERA18FA194
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. 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: 8569f8c3bf98759fa95e32a784d86d06c6a36d290f4fef5095d9b21c97d94140; retrieved 2026-09-13T18:10:03.861Z.