CEN26LA045 · Cessna TU206F
Cessna TU206F and Vette Collect Aviation Hawker Beechcraft Corp B300 · Accident: ground collision while taxiing
Event
- NTSB case
- CEN26LA045
- 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
- Ongoing
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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
Aircraft 1 · Cessna TU206F
- Aircraft type
- Cessna 206
- 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
- N37EW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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
- Taxi
- 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
- Ground collision
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Hawker Beechcraft Corp B300
- Aircraft type
- Beechcraft 300
- 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
- N545KA
- Operator
- Vette Collect Aviation
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 18 years (built 2007)
- 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
- Unknown
- 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
- Airport occurrence
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On November 12, 2025, about 14:10 central standard time, a Cessna TU206F, N37EW, and a Hawker Beechcraft Corp B300, N545KA, were substantially damaged when they were involved in an accident at Muscatine Regional Airport (MUT), Muscatine, Iowa. The pilot and passenger of the TU206F were not injured, and the pilot, check airman, and FAA observer of the B300 were also not injured. The TU206F and B300 were operated as a Title 14 Code Of Federal Regulations Part 91 personal flights. According to the pilot of TU206F, before crossing runway 06/24, he visually cleared the runway of any traffic. He then made a radio call on the common traffic advisory frequency stating that he was crossing runway 06/24 at taxiway Bravo. He stated that he did not hear any radio transmissions from the B300 before the accident. According to the pilot of the B300, he was conducting a simulated single-engine approach for the ILS runway 24. He reported that he made a radio call on the common traffic advisory frequency after passing the final approach fix, and on short final to runway 24. During the landing roll, he saw an airplane taxiing across the runway from left to right. He attempted to avoid colliding with the TU206F by veering left. The pilot stated that he did not hear the TU206F make a radio call before crossing the runway. The B300 impacted the empennage of the TU206F with its right wing at the intersection of runway 24 and taxiway B. The TU206F sustained substantial damage to its empennage, and the B300 sustained substantial damage to its right wing. A video recording of the accident was gathered for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN26LA045
- Event ID
- 20251112201997
- Case number
- CEN26LA045
- 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, coordinates. 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: 98ba3fa9d049ffa53861d9d8406d2d0f5a64bb3e326c1a7ba493fe1b2ff46f20; retrieved 2026-09-13T18:51:18.202Z.