NYC96LA133 · Piper PA-28-161
Piper PA-28-161 · Accident: hard landing
From Igor I Sikorsky Memorial Airport (BDR) to Igor I Sikorsky Memorial Airport (BDR)
Event
- NTSB case
- NYC96LA133
- 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-28-161
- Aircraft type
- Piper PA-28
- 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
- N8119H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Igor I Sikorsky Memorial Airport (BDR)To Igor I Sikorsky Memorial Airport (BDR)
- 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
- 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 › Flare, improper
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of Bridgeport, CT, the place the record names. Not the accident site.
NTSB narrative
The student pilot had done 4 touch-and-go landings with an instructor aboard. The instructor deplaned, and the student conducted his first solo flight; he resumed doing touch-and-go landings. The student reported: 'After the first touch-and go-landing, I departed for left closed traffic for my second touch-and-go. While reporting mid-field, downwind as instructed during take-off clearance, I was informed that I was number 2 in sequence to follow traffic on right base for runway 11, and to extend my downwind leg, which I proceeded to do. Final glide path was established, aircraft was trimmed, everything looked good. Final approach was made with the engine at idle. Airspeed was bleeding off, and over the numbers was reading about 65 knots, a little high, but did not seem to be a problem. Everything looked good for the touch and go on the touchdown zone. When I touched down the aircraft ballooned. I flared and the plane ballooned again. I felt the plane was down; however, it ballooned again, and on the third attempt to land, the aircraft touched down on the nose wheel. The nose wheel tire blew, causing the propeller to strike the runway. At no time did I feel that the plane was out of control. I was able to maintain directional control and was able to clear the runway at (the taxiway). I brought the aircraft to a stop, secured it using shut-down check-list procedures.' The student reported no mechanical malfunction.
Probable cause
the student pilot's improper flare and improper recovery from a bounced landing, which resulted in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA133
- Event ID
- 20001208X06093
- Case number
- NYC96LA133
- 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: a44fafb21361c3473c004bda914ed0ba52673173bb29b2edbc34207dc0cad75e; retrieved 2026-09-22T22:05:30.222Z.