ERA17LA063 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of control on ground during takeoff
From Mercer County Airport (BLF) to Hilton Head Airport (HXD)
Event
- NTSB case
- ERA17LA063
- 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
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- 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
- N217CE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mercer County Airport (BLF), Bluefield, WVTo Hilton Head Airport (HXD), Hilton Head Island, SC
- Aircraft age
- About 5 years (built 2011)
- 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 · rejected 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
- 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 commercial pilot stated that, during the takeoff roll, the engine was not producing full power and the airspeed was fluctuating, so he chose to abort the takeoff. He reduced power and applied full braking, but the left wing became airborne, and the right wing struck the runway. The airplane veered right, and the propeller struck a grassy area.
Postaccident examination of the airplane revealed substantial damage to the right wing and the engine mounts. Postaccident engine examination found that the engine's magneto timing was set incorrectly; no other evidence of any preimpact mechanical malfunctions or failures were found that would have precluded normal operation. During a subsequent test-run of the engine with the magneto timing set to its preaccident state, the engine started immediately and ran continuously at all power settings without interruption.
Performance data downloaded from the on-board recording devices revealed that the pilot did not add full power until the airplane was about 15% down the runway. The engine performance data also revealed that associated engine parameters moved in response to rpm increases and decreases. Although the pilot reported that the engine was not producing full rpm and that the airspeed was fluctuating during the attempted takeoff, the recorded performance data revealed that the engine was achieving close to full power, and there was no evidence of a power loss. Further, the airspeed was sufficient for takeoff with no fluctuations noted before the pilot chose to gradually reduce power. Therefore, given the evidence, it is likely that the engine and airplane were functioning adequately before the pilot decided to abort the takeoff. After the pilot decided to abort the takeoff, he failed to maintain directional control of the airplane.
Probable cause
The pilot's failure to maintain directional control during the aborted takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17LA063
- Event ID
- 20161129X20345
- Case number
- ERA17LA063
- 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: 8337fd5ec93dd67a8a5467670239ccc0935e8f1d87026a051042eb0316976a5d; retrieved 2026-09-16T04:51:53.949Z.