ERA09CA489 · Piper J5A
Piper J5A · Accident: ground collision during landing
From Southbridge Municipal Airport (3B0) to Skylark Airpark (7B6)
Event
- NTSB case
- ERA09CA489
- 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
- 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
Piper J5A
- Aircraft type
- Piper J5
- 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
- N33078
- Operator
- Horan Mark e
- Onboard fatalities
- Unknown
- Route
- From Southbridge Municipal Airport (3B0), Southbridge, MATo Skylark Airpark (7B6), Warehouse Point, CT
- 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
- Landing · flare/touchdown
- 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
- Ground 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
- Aircraft › Fluids/miscellaneous hardware
- 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 pilot stated that he began the day with an unknown quantity of fuel. Shortly after departing on his second flight of the day, the airplane suffered a complete loss of engine power. During the subsequent forced landing, the left main landing gear caught tall grass and ground-looped the airplane, which resulted in substantial damage to the left landing gear, left wing strut, and left lower fuselage. Post accident examination of the wreckage by a Federal Aviation Administration (FAA) inspector revealed no odor of fuel, no fuel spillage, and 5 ounces of fuel in the airplane. The pilot reported that there were no mechanical deficiencies with the airplane.
Probable cause
A loss of engine power due to fuel exhaustion. A factor in the accident was the pilot's inadequate preflight inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA489
- Event ID
- 20090828X62325
- Case number
- ERA09CA489
- 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: 54b6542064a518343a184cb72f775d78088183b2330ea62bb7947699572763c4; retrieved 2026-09-15T12:51:51.961Z.