NYC93LA088 · Piper PA-23-150
Piper PA-23-150 · Accident: in flight collision with object while maneuvering
From W36 · Chesapeake, VA to Indianapolis Regional Airport (MQJ)
Event
- NTSB case
- NYC93LA088
- 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-23-150
- Aircraft type
- Piper PA-23
- 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
- N1494P
- Operator
- Guckelberg, Frederich A. · private individual
- Onboard fatalities
- Unknown
- Route
- From W36 · Chesapeake, VATo Indianapolis Regional Airport (MQJ), MT. COMFORT, IN
- 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
- Maneuvering · turn to reverse direction
- 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
- In flight collision with object
- 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
- Tree(s)
- 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
- Pilot in command › Altitude, inadequate
- Pilot in command › In-flight planning/decision, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THAT HE PLANNED A VFR FLIGHT AT 1000 FT AGL. HIS ROUTE OF FLIGHT WAS OVER HILLY TERRAIN. HE SAID THAT 'CLIMB PERFORMANCE WAS NOTICEABLY LOW AND...SMOKE [WAS COMING] FROM THE LEFT ENGINE.' HE ENTERED A MOUNTAIN PASS AND DISCOVERED HE COULD NOT FIND AN EXIT FROM THE HIGH TERRAIN. THE PILOT MADE A SHARP TURN TO MANEUVER AWAY FROM THE HILLS. WITNESSES SAW THE AIRPLANE FLYING AT LOW ALTITUDE AND THEN SAID IT 'STARTED A TURN TO THE LEFT AND THEN WENT STRAIGHT DOWN, NOSE FIRST.' THEY SAID NOTHING ABOUT SEEING 'PLUMES OF BLACK SMOKE,' OR HEARING ABNORMAL ENGINE SOUNDS. THE LEFT ENGINE WAS EXAMINED, AND EXCEPT FOR ONE MAGNETO THAT WAS NOT FUNCTIONING, NOTHING WAS FOUND THAT WOULD HAVE PREVENTED THE ENGINE FROM RUNNING.
Probable cause
THE PILOT'S INADEQUATE INFLIGHT DECISION AND PLANNING, AND HIS FAILURE TO MAINTAIN AN ALTITUDE ADEQUATE FOR TERRAIN AVOIDANCE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93LA088
- Event ID
- 20001211X12231
- Case number
- NYC93LA088
- 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: 1d96c967236697da2269bd00f4a2c88e2b37212f45bbbe4053ed6c8c7d1d9f7c; retrieved 2026-09-21T14:28:14.436Z.