CEN09FA015 · Cessna 150G
Cessna 150G · Accident: collision during takeoff/landing during initial climb
From Cedar Lake, MI (private airstrip) to Clare Municipal Airport (48D)
Event
- NTSB case
- CEN09FA015
- 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
- 1 · 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 150G
- 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
- N3623J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cedar Lake, MI (private airstrip)To Clare Municipal Airport (48D), Clare, MI
- 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
- Defining eventThe 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that the southeasterly grass runway (2,331 feet by 100 feet) was "very bumpy" and that it took more than half of the available runway length to achieve liftoff. After liftoff, the airplane did not clear the 60/70-foot-high tree line located at the departure end of the runway, and impacted several trees before descending nose first into a residential backyard. A review of downloaded GPS data showed the airplane began its takeoff roll from the approach end of the runway. Approximately 34 seconds into the takeoff, the airplane had traveled about 1,788 feet laterally, over 3/4 of the runway length, and had climbed 5 feet above the airport elevation. The plotted data showed that the airplane completed a 10-degree right turn immediately after liftoff and continued to climb as it approached the tree line. Between the last two data points, the airplane’s average ground speed was approximately 53 knots. The last data point was approximately 68 feet above the airport elevation and 223 feet laterally from the accident site. The aircraft’s weight before the accident flight was at or near the certified maximum takeoff weight. Based on the available airport and weather information, the airplane’s pilot operating handbook indicated that the takeoff ground roll, on a level grass runway without a headwind, was about 885 feet, and the required distance to clear a 50-foot obstacle was about 1,663 feet. A review of the maintenance records found no history of unresolved airworthiness issues, and examination of the recovered wreckage revealed no evidence of a pre-impact mechanical malfunction. The accident engine demonstrated the ability to produce rated horsepower during a post-accident test run. The student pilot had accumulated 25.3 hours total flight time, of which 13.9 hours were documented as pilot-in-command.
Probable cause
The student pilot's failure to maintain adequate clearance after takeoff. Contributing to the accident was the pilot's overall lack of flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09FA015
- Event ID
- 20081014X91018
- Case number
- CEN09FA015
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 561152427c48cd8887385b9a01f98c3ca778b657e9b294a8bc894a05582a7aca; retrieved 2026-09-13T19:33:34.459Z.