ERA16FA324 · Cessna 120
Cessna 120 and Piper PA28 140 · Accident: midair collision en route
Event
- NTSB case
- ERA16FA324
- 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
- 3 · 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 · Cessna 120
- Aircraft type
- Cessna 120
- 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
- N3580V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hamburg Inc Airport (4G2), Hamburg, NYTo St Marys Municipal Airport (OYM), Saint Marys, PA
- Aircraft age
- About 68 years (built 1948)
- 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 · Piper PA28 140
- Aircraft type
- Piper PA28
- 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
- N612FL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hamburg Inc Airport (4G2), Hamburg, NYTo St Marys Municipal Airport (OYM), Saint Marys, PA
- Aircraft age
- About 45 years (built 1971)
- 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
The accident airplanes were the first two of a flight of six that were travelling to another airport for the pilots and passengers to have breakfast together. The first airplane departed first as it was a slower airplane and required more time to fly to the destination airport. The second airplane departed about 1 minute 18 seconds later. Radar data indicated that that the second airplane was behind and to the left of the first airplane, until they collided at 3,500 ft mean sea level. It could not be determined why the pilot of the second airplane did not see and avoid the first airplane prior to the collision. Both airplanes then entered a near-vertical, nose-down descent. Examination of the wreckage revealed that the second airplane's propeller sliced through the first airplane's empennage, and the first airplane subsequently contacted the second airplane's left wing with its tire, severing an outboard section. No preimpact mechanical malfunctions were identified with the wreckages of both airplanes that would have precluded normal flight.
Probable cause
The failure of the second airplane's pilot to see and avoid the first airplane as he was overtaking the first airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA324
- Event ID
- 20160926X05138
- Case number
- ERA16FA324
- 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: b0431469658277f62618a2466a06eb60dac57813bd47e6bdf5ff21c4b894b4c7; retrieved 2026-09-13T18:09:12.655Z.