FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC02LA069 · Piper P46T

8 Mar 2002 · Philadelphia, PA, United States

Piper P46T · Accident: loss of control on ground/water during landing

From Igor I Sikorsky Memorial Airport (BDR) to Northeast Philadelphia Airport (PNE)

Report a problem

Event

NTSB case
NYC02LA069
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 P46T

Aircraft type
Piper P46
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
N117NU
Operator
Unknown
Onboard fatalities
Unknown
Route
From Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CTTo Northeast Philadelphia Airport (PNE), Philadelphia, PA
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
Loss of control on ground/water
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 › Recovery from bounced landing, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was landing on runway 06. The pilot reported that he was high and fast. He did not flare, and the airplane touched down, nose gear first, and bounced. The pilot added power for a go-around, and then aborted the go-around. The airplane then touched down again, veered off the left side of the runway, traveled through 380 feet of dirt and came to rest in a grassy area. Both main landing gear had collapsed to the right, and the nose landing gear was bent to the right. The left wing had wrinkles in the upper surface of the skin, as well as damage to the flap and aileron. All propeller blades had damage to the tips. Weather reported about the time of the accident included winds from 060 degrees at 5 knots, with clear skies.

Probable cause

The pilot's improper recovery from a bounced landing. A factor was the pilot's failure to flare during initial touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC02LA069
Event ID
20020318X00355
Case number
NYC02LA069
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, 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: 609f808d0b5eec65fe5c2d3fd02165e8d55e65ced19b0f06b9d5cc5961194bf6; retrieved 2026-09-22T11:04:49.382Z.