NYC96LA146 · Cessna 172H
Cessna 172H · Accident: in flight collision with object during initial climb
From an unrecorded airport to Titusville Airport (6G1)
Event
- NTSB case
- NYC96LA146
- 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 172H
- Aircraft type
- Cessna 172
- 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
- N1412F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Titusville Airport (6G1), Titusville, PA
- 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 airplane had been landed by another pilot in a nearby field earlier that day due to fuel exhaustion. According to the accident pilot, he added 10 gallons of fuel, did a preflight that consisted of determining the takeoff distance and the airplane weight and balance. He also 'paced off the road and looked for any obstructions that could interfere with the takeoff roll.' An engine runup was conducted before the takeoff. The pilot reported he used the short field takeoff procedure, and the takeoff roll was normal. During the initial climb the airplane struck the top wire of a transmission line, which caused the airplane to turn left and impact the ground.
Probable cause
the pilot's failure to assure that adequate takeoff distance was available to clear an obstacle.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC96LA146
- Event ID
- 20001208X06342
- Case number
- NYC96LA146
- 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: e8dfdad68aa50a58ec802b1514eec6bdb1f36e1875fcea32d0e364348576173b; retrieved 2026-09-22T21:58:35.096Z.