ERA11FA291 · Piper PA-28-180
Piper PA-28-180 and Piper PA-24-250 · Accident: midair collision en route
Event
- NTSB case
- ERA11FA291
- 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
- 2 · 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 PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N5275L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (MGJ), Montgomery, NYTo Sussex Airport (FWN), Sussex, NJ
- 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 · 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
- Substantial
Aircraft 2 · Piper PA-24-250
- Aircraft type
- Piper PA-24
- 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
- N7757P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (MGJ), Montgomery, NYTo Sussex Airport (FWN), Sussex, NJ
- 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 · 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
- Substantial
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The two accident pilots arrived at the airport in a Piper PA-24-250 (PA24), with the intention that one of the pilots would ferry a Piper PA-28-180 (PA28) back to the departure airport. The PA28 departed first for the return flight, followed by the PA24; however, the PA24 was faster and caught up to the PA28 within 5 minutes. The PA24 approached from below and behind the PA28 and was likely not visible to the pilot of the PA28.
Witnesses near the accident site observed the airplanes flying in the same direction when they "clipped" each other. The PA28 entered an immediate right spiraling dive, while the PA24 entered an "angled nose dive" toward the ground. The PA28 was found inverted with the fuselage crushed; the outboard portion of the right wing was separated and showed damage consistent with propeller strikes to the aft wing spar and flap. The majority of the PA24 was consumed by a postimpact fire. Examination of both airplanes revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
It was not known if the accident pilots were attempting formation flight or were in communication with each other. However, 14 Code of Federal Regulations (CFR) 91.111(a) states that "no person may operate an aircraft so close to another aircraft as to create a collision hazard." In addition, 14 CFR 91.113 stipulates that the pilot of an overtaking airplane (in this case, the PA24) “shall alter course...to pass well clear” of the overtaken airplane. The PA24 should not have passed over, under, or ahead of the PA28 unless it was well clear.
Probable cause
The failure of the PA24 pilot to maintain adequate clearance from the PA28 resulting in an inflight collision. Contributing to the accident was the PA24 pilot's decision to overtake the PA28.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11FA291
- Event ID
- 20110509X84024
- Case number
- ERA11FA291
- 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, coordinates. 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: 9b1fc74dc2ec424e009e43ab88d10e7e264efd5e40c900741cd8b3bc0b12af07; retrieved 2026-09-13T18:05:38.637Z.