NYC94LA136 · Piper PA-34-200T
Piper PA-34-200T · Accident: hard landing
From General Mitchell International Airport (MKE) to an unrecorded destination
Event
- NTSB case
- NYC94LA136
- 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-34-200T
- Aircraft type
- Piper PA-34
- 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
- N40996
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From General Mitchell International Airport (MKE), Milwaukee, WITo 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Destroyed
Cause areas
- Pilot in command › Directional control, not maintained
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of Lumberton, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PILOT COMPLETED A CIRCLING APPROACH TO RUNWAY 01. DURING THE TOUCHDOWN, THE AIRPLANE BOUNCED THREE TIMES. THE PILOT ELECTED TO ABORT THE LANDING AND APPLIED FULL POWER. THE AIRPLANE VEERED TO THE LEFT AND STRUCK TREES. THE FAA INSPECTOR STATED IN HIS REPORT, 'PILOT LOST CONTROL OF AIRCRAFT WHEN APPLYING FULL POWER WHILE RECOVERING FROM LAST BOUNCE. [HE] ATTEMPTED A GO-AROUND. [THE] AIRCRAFT BANKED STEEPLY TO LEFT AND IMPACTED TREES.'
Probable cause
The pilot's (1) improper recovery from a bounced landing and (2) failure to maintain directional control during an aborted landing. A factor is the pilot's improper landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC94LA136
- Event ID
- 20001206X01847
- Case number
- NYC94LA136
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1994-07-25.
- API snapshot SHA-256: 69a4e51f31f545e9ab295219fe89983e5bef8ea714ea04adc3e64f06b4bb7677; retrieved 2026-09-21T13:45:03.657Z.