NYC93LA142 · Cessna 152L
Cessna 152L · Accident: in flight collision with object during initial climb
From an unrecorded airport to MHT · MANCHESTER, MA
Event
- NTSB case
- NYC93LA142
- 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
Cessna 152L
- 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
- N10489
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo MHT · MANCHESTER, MA
- 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
- Initial climb
- 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
- 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 › Preflight planning/preparation, inadequate
- Pilot in command › Proper climb rate, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE DEPARTED FROM A 1400 FOOT GRAVEL RUNWAY TOWARD RISING TERRAIN. THE PILOT STATED THAT AFTER CROSSING THE DEPARTURE END OF THE RUNWAY THE AIRPLANE CEASED CLIMBING. THE AIRPLANE STRUCK A 5-FOOT POLE, 20 FEET ABOVE THE AIRPORT ELEVATION, 600 FEET FROM THE DEPARTURE END OF THE RUNWAY. THE PILOT CALCULATED THE TAKEOFF WEIGHT TO BE 38 POUNDS UNDER THE MAXIMUM. ACCORDING TO THE PILOT OPERATING HANDBOOK, THE AIRPLANE REQUIRED A GROUND ROLL OF 900 FEET FOR A SHORT FIELD TAKEOFF, AND 1660 FEET TO CLEAR A 50 FOOT OBSTACLE. THE AIRPLANE STRUCK THE POLE APPROXIMATELY 2000 FEET FROM THE APPROACH END OF THE DEPARTURE RUNWAY.
Probable cause
the pilot's inadequate preflight planning for a departure from a short field and his failure to attain a proper climb rate, resulting in an in-flight collision with a 5 foot pole located on rising terrain, 20 feet above the airport elevation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC93LA142
- Event ID
- 20001211X13222
- Case number
- NYC93LA142
- 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: f5cd851291a74803ac8276314c330f4e79d0714a8eb131f0a9c5c166f393b8f6; retrieved 2026-09-23T01:47:30.373Z.