NYC97LA056 · Cessna 150
Cessna 150 · Accident: loss of control on ground/water during takeoff
From MD24 to an unrecorded destination
Event
- NTSB case
- NYC97LA056
- 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 150
- Aircraft type
- Cessna 150
- 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
- N11438
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From MD24To 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
- Takeoff · roll/run
- 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 › Aborted takeoff, not performed
- Pilot in command › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft veered off the runway during the takeoff roll and collided with trees. According to the pilot, 'we did a normal run up at the point half way up the hill on runway 13. Everything looked okay, controls worked okay, carburetor heat and magnetos checked okay. We taxied to the top of the hill and attempted to take off. Within seconds after we started to roll on runway 13, the airplane veered to the left. I applied full right rudder. The airplane straightened out but it had gone too far left. With the right pedal on the floor, the airplane had straightened out fairly close to a line of small pine trees on the left side of the runway. The airplane continued parallel to the trees for about 100 feet even though I continued full right rudder. Finally, the airplane turned left into the trees.' The pilot further stated that he 'should have pulled power immediately when [the] airplane went out of control.'
Probable cause
The pilot's failure to maintain directional control and failure to abort the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA056
- Event ID
- 20001208X07453
- Case number
- NYC97LA056
- 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: 2cab32f9c67a1aaee7e06120c44bb7513c7446917d83822f92e2e5e5875dd963; retrieved 2026-09-22T20:19:01.138Z.