ERA14CA430 · Cessna 172M
Cessna 172M · Accident: controlled flight into terrain/object (CFIT) during initial climb
From Danbury Municipal Airport (DXR) to Waterbury Airport (N41)
Event
- NTSB case
- ERA14CA430
- 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
- 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 172M
- 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
- N20469
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Danbury Municipal Airport (DXR), Danbury, CTTo Waterbury Airport (N41), Waterbury, CT
- Aircraft age
- About 42 years (built 1972)
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was utilizing an iPad for navigation, and mistakenly landed in a field rather than his intended destination, an airport with a turf runway. After landing, he taxied the airplane to a corner of the field and commenced a takeoff roll, estimating the available takeoff distance to be about 600 feet. Just after takeoff, the left wing struck a tree and the airplane subsequently impacted the ground, resulting in substantial damage to the left wing and engine firewall. The pilot reported no mechanical malfunctions or abnormalities with the airplane that would have precluded normal operation.
Probable cause
The pilot's decision to takeoff from a field which resulted in a collision with trees and the ground. Contributing to the accident was the pilot's failure to correctly identify the destination airport and runway, which resulted in an off-airport landing in the field.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA430
- Event ID
- 20140909X30110
- Case number
- ERA14CA430
- 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: 26a58c15ed79792d534ae058a7d77da8fb7d6a849d1fce590ab5db7e8e840612; retrieved 2026-09-16T01:44:13.052Z.