NYC06CA109 · Cessna 152
Cessna 152 · Accident: in flight collision with object during landing
From Perkiomen Valley Airport (N10) to Northumberland County Airport (N79)
Event
- NTSB case
- NYC06CA109
- 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
Cessna 152
- Aircraft type
- Cessna 152
- 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
- N4732Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Perkiomen Valley Airport (N10), Collegeville, PATo Northumberland County Airport (N79), Shamokin, 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 · aborted
- 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 › Flaps, improper use of
- Pilot in command › Recovery from bounced landing, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot of the Cessna 152 was landing on a 3,297-foot-long runway. She reported that when the airplane touched down, it began to porpoise. She was not able to correct the bouncing, and elected to abort the landing. The pilot stated she "panicked" when she observed trees located off the end of the runway, and mistakenly retracted the flaps completely. The airplane climbed slowly, and impacted trees off the left side of the runway. It then nosed over, and impacted the ground. Examination of the airplane did not reveal any mechanical malfunctions, nor did the pilot report any. The pilot reported 140 hours of total flight experience, which included about 120 hours in the same make and model.
Probable cause
The pilot's failure to recover from a bounced landing, and her improper use of flaps during an aborted landing, which resulted in an in-flight collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06CA109
- Event ID
- 20060608X00722
- Case number
- NYC06CA109
- 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: 892021dd4bfca99ec494396e7412c223165dcaeb8ba72bbd491c8793e62d305c; retrieved 2026-09-21T08:58:31.834Z.