IAD00LA084 · Cessna 150G
Cessna 150G · Accident: in flight collision with object during initial climb
From No airport to Frederick Douglass Greater Rochester International Airport (ROC)
Event
- NTSB case
- IAD00LA084
- 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 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
- N8376J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From No airportTo Frederick Douglass Greater Rochester International Airport (ROC), Rochester, NY
- 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
- 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
- Wire, transmission
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot/owner initiated a takeoff from a grass field that was 1,100 feet in length. He said he deployed 10 degrees of flaps and used a soft field technique for takeoff. The pilot said the airplane produced full power during the takeoff roll and climbed immediately after takeoff. However, the airplane was unable to climb over the obstacles at the departure end of the runway. The airplane struck wires, collided with terrain, and came to rest inverted. The pilot reported that there were no mechanical deficiencies with the airplane. Examination of the airplane by FAA inspectors revealed the wing flaps were in the fully retracted position. Interpolation of performance charts in the owner's manual revealed that the total takeoff distance required to clear a 50-foot obstacle was 1,671 feet.
Probable cause
the pilot's inadequate preflight performance planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD00LA084
- Event ID
- 20001212X21994
- Case number
- IAD00LA084
- 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: 906a2bfb494a47b80946e7d7c70623c38802925d398a0450da91567ffb924d57; retrieved 2026-09-22T12:26:17.702Z.