NYC83LA070 · Cessna 152
Cessna 152 · Accident: in flight collision with terrain/water during initial climb
From Bally, PA to an unrecorded destination
Event
- NTSB case
- NYC83LA070
- 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 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
- N25565
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bally, PATo 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
- 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 terrain/water
- 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
- Stall/mush
- 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 › Airspeed, inadequate
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE INITIATED HIS TAKEOFF FROM THE 1300 FT/BLACKTOP PORTION OF A 2500 FT RUNWAY. THE REMAINDER OF THE RUNWAY WAS SOD. HE STATED THAT HE ROTATED FOR TAKEOFF ABOUT 50 FT FROM THE END OF THE BLACKTOP PORTION AT 56 TO 58 KTS. ALSO, HE REPORTED THAT AS THE PLANE PASSED OVER THE END OF THE BLACKTOP, IT SEEMED TO LOSE LIFT AND THE LEFT WING DROPPED. SUBSEQUENTLY, THE LEFT MAIN GEAR STRUCK SNOW ON THE SIDE OF THE SOD PORTION AND THE PLANE VEERED TO THE LEFT. IT THEN DROPPED ONTO THE NOSE GEAR AND CONTINUED FOR ABOUT 100 FT AT A 30 DEG ANGLE FROM THE RUNWAY. THE NOSE GEAR COLLAPSED AND THE PLANE NOSED DOWN, THEN SETTLED BACK ON THE MAIN GEAR.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83LA070
- Event ID
- 20001214X42300
- Case number
- NYC83LA070
- 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: 7128ab5043e07aa7d5e988d509587b31e69c0dcca03a6257e3806de6319dd228; retrieved 2026-09-23T23:04:40.483Z.