CHI07FA022 · Cessna T303
Cessna T303 · Accident: loss of control in flight en route
From South Bend International Airport (SBN) to Ankeny Regional Airport (IKV)
Event
- NTSB case
- CHI07FA022
- 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
- 5 · 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 T303
- Aircraft type
- Cessna 303
- 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
- N611BB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From South Bend International Airport (SBN), South Bend, INTo Ankeny Regional Airport (IKV), Ankeny, IA
- 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
- En route · climb to cruise
- 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 in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aircraft control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed his home airport at 0502 and landed at another airport where he picked up employees of a marketing company to fly them to an out of state meeting. The accident occurred at 2003 shortly after taking off on the return trip to fly the employees back home. Shortly before departure a fourth passenger was added to the flight after his commercial flight was cancelled. A person who worked for the fixed base operator at the departure airport stated the pilot looked tired or just ready to go home. The pilot received his clearance for the IFR flight prior to takeoff. The pilot misread the clearance back to the controlled and was corrected. Radar data showed the pilot initially flew the assigned south-southwest heading prior to the airplane turning right to a westerly heading. The controller queried the pilot and issued a heading to intercept the VOR. The pilot corrected the heading and shortly thereafter the airplane once again began a right turn back toward the west. The airplane continued to climb throughout the heading changes. Radar data showed the airplane then began another left turn during which time it entered a spiraling rapid descent. According to weather data, the airplane was in instrument meteorological conditions when this occurred. The airplane impacted the terrain in an open cornfield. Weight and balance calculations indicate the airplane was at least 383 pounds over gross weight. Post accident inspection of the airplane and engines did not reveal any preexisting failure/malfunction.
Probable cause
The pilot became spatially disoriented and as a result failed to maintain control of the airplane. Factors associated with the accident were the instrument meteorological conditions aloft and the pilot being fatigued.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07FA022
- Event ID
- 20061117X01689
- Case number
- CHI07FA022
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-11-14.
- API snapshot SHA-256: 7ee2746d74e70d5585280d58f20949f9a06cf2fb43ef11a09be8f3a68198ea16; retrieved 2026-09-20T16:59:24.089Z.