NYC83FA050 · Piper PA-30
Piper PA-30 · Accident: partial loss of engine power (non-mechanical) during initial climb
From Orange County Airport (MGJ) to an unrecorded destination
Event
- NTSB case
- NYC83FA050
- 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
Piper PA-30
- Aircraft type
- Piper PA-30
- 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
- N223JN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (MGJ), Montgomery, NYTo not recorded
- 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
- Initial climb
- 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
- Partial loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation; Fuel exhaustion
- 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
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT EXPERIENCED A POWER LOSS ON ONE ENGINE DURING TAKE-OFF INITIAL CLIMB. THE PILOT REGAINED CONTROL OF THE ACFT AND CONTINUED TO FLY THE LANDING PATTERN. ON THE DOWNWIND LEG THE ENGINES RAN INTERMITTENTLY. TURNING FINAL BOTH ENGINESSTOPPED. A FORCED LANDING WAS MADE IN AN OPEN PASTURE 1500 FEET SHORT OF THE RUNWAY. THE PILOT STATED THAT HE REFUELED BY THE TIME FLOWN AND FIGURED 15 GALLONS OF FUEL AN HOUR AS AN AVERAGE CONSUMPTION. ON THIS FLIGHT HE WAS GOING ONCE AROUND THE PATTERN. HE ESTIMATED THE MAIN TANKS TO HAVE 7 GALLONS EACH. WHEN ASKED HOW HE ARRIVED AT THAT ESTIMATE HE SAID 'WHEN HE LOOKED INTO THE MAIN TANKS HE WANTED TO SEE 7 GALLONS AND THATS WHAT HE SAW.' DURING THE FORCED LANDING THE LANDING GEAR WAS DAMAGED AND THE ACFT COLLIDED WITH A TREE WHICH SEPARATED A WING. BOTH OCCUPANTS RECEIVED MINOR INJURIES. AFTER THE ACCIDENT THE MAIN TANKS CONTAINED LESS THAN A PINT OF FUEL. THE AUX. TANKS CONTAINED ONE GALLON EACHTHE TANK SELECTOR WAS POSITIONED TO THE MAIN TANKS. THE PILOT SAID HE HAD PLANNED TO REFUEL AFTER THIS FLIGHT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA050
- Event ID
- 20001214X42072
- Case number
- NYC83FA050
- 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: 0609732601c64c91a6d76d61c8ef28c806e02bcfd878d75a06953a0ae2026a96; retrieved 2026-09-22T02:48:26.206Z.