ERA14CA352 · Cessna 172M
Cessna 172M · Accident: loss of control on ground during takeoff
From Chatham Municipal Airport (CQX) to Chatham Municipal Airport (CQX)
Event
- NTSB case
- ERA14CA352
- 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
- N1066R
- Operator
- Ford James C
- Onboard fatalities
- Unknown
- Route
- From Chatham Municipal Airport (CQX), Chatham, MATo Chatham Municipal Airport (CQX), Chatham, MA
- Aircraft age
- About 40 years (built 1974)
- 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
- 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
- Loss of control on ground
- 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
According to the pilot, he was performing a touch-and-go landing to runway 24. He was initially high on final; however, he landed the airplane about 400 feet from the arrival end of the runway. After applying full throttle during the subsequent takeoff, the airplane veered "significantly" to the left. He attempted to regain directional control; however, the airplane departed the left side of the runway, into the grass. He applied wheel brakes and the wheels skidded on the grass until the airplane contacted trees. The airplane then spun around "violently" and came to a stop. An inspector from the Federal Aviation Administration examined the airplane and confirmed substantial damage to the fuselage and wings. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's failure to maintain directional control during takeoff, resulting in a runway excursion and collision with trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA352
- Event ID
- 20140724X85239
- Case number
- ERA14CA352
- 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: cf14de312a0e29138c4a69fbfb4b13356dbe38066e3645d25df7c562bc6b7c97; retrieved 2026-09-16T00:59:04.164Z.