CHI01FA169 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: loss of control on ground/water during landing
From Chariton Municipal Airport (CNC) to Springfield Branson National Airport (SGF)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CHI01FA169
- 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 Possible conflict
- 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
- N739BB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chariton Municipal Airport (CNC), Chariton, IATo Springfield Branson National Airport (SGF), Springfield, MO
- 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
- Landing
- 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
- Pilot in command › Lack of experience
Approximate · Estimated position: the centre of Springfield, MO, the place the record names. Not the accident site.
NTSB narrative
The pilot took delivery of the new airplane and completed a three-day flight training program specific to the accident airplane model a day prior to the accident. The pilot reported bouncing the airplane during landing while landing at an en route stop. The flight then departed and continued onto the accident airport where the pilot bounced the airplane and attempted to execute a go-around from which the airplane reportedly pitched up rapidly and veered to the left, off the runway. The pilot reportedly reduced power and used brakes to slow the airplane down, but the airplane continued to travel across the airport striking a disabled airplane used for airport rescue and fire fighting (ARFF) training. The right front passenger received serious facial injuries. Post accident testing of the right front passenger's inertia reel did not pass test parameters. The landing attitude, as viewed from the cockpit, was reported by the pilot to appear as if the airplane was in a nose down to level attitude and different from other airplanes. The manufacturer of the airplane has documented eight propeller strikes and six tail strikes in the accident make of the airplane by both low and high time pilots.
Probable cause
the lack of experience in the type of airplane and directional control not maintained by the pilot. The improper flare and parked airplane were contributing factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01FA169
- Event ID
- 20010620X01213
- Case number
- CHI01FA169
- 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: 9620b9759a27302c03cb12deb7389c9fc9f054554f34f3cad880d65caf1948fe; retrieved 2026-09-21T10:03:24.900Z.