NYC00LA211 · Cessna 150
Cessna 150 · Accident: overrun during takeoff
From Miller Farm Landing Strip (7B4) to Lancaster, OH (no airport)
Event
- NTSB case
- NYC00LA211
- 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
- N6639F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Miller Farm Landing Strip (7B4)To Lancaster, OH (no airport)
- 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 · rejected takeoff
- 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
- Overrun
- 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, delayed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot performed all items on the checklist, and did not notice any discrepancies during the run-up. He taxied onto a 3,250-foot long, 50-foot wide, turf runway. The student pilot held the brakes, applied power, and performed a soft field takeoff. He rotated the airplane at 55 mph, and then lowered the nose to gain airspeed. About 5-10 feet in the air, at 62 mph, the airplane felt like it did not have the usual power. The student pilot observed a tachometer indication of 2,250 rpm, and the airplane did not gain airspeed or altitude. The student pilot aborted the takeoff with approximately 1,000 feet of runway remaining. The airplane touched down, skidded on wet grass, traveled off the end of the runway, and struck trees. Examination of the wreckage did not reveal any pre-impact mechanical malfunctions. Review of a Cessna 150 manual revealed that during takeoff, the engine should run smoothly at 2,375 to 2,475 rpm with carburetor heat off.
Probable cause
The pilot's delay in aborting the takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00LA211
- Event ID
- 20001212X21593
- Case number
- NYC00LA211
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-07-22.
- API snapshot SHA-256: 19813142fecb134e4706775f33422cee6f76439a9fce267ade9a9bac09099ceb; retrieved 2026-09-22T12:39:55.778Z.