Cessna TU206F and Hawker Beechcraft CORP B300 accident near Muscatine, Iowa, November 12, 2025
On November 12, 2025 at about 8:10 pm local time, 2 aircraft, Cessna TU206F (N37EW) and Hawker Beechcraft CORP B300 (N545KA), were involved in the same accident near Muscatine, Iowa (Muscatine Municipal Airport). No one was hurt; 5 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 12, 2025 · about 8:10 pm local time · cases in 2025
- Place
- Muscatine, Iowa · Muscatine Municipal Airport · cases near this airport · map
- Type
- Accident · collision on the ground
- Injuries
- No one was hurt; 5 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Cessna TU206F · all TU206Fs on the register
- Registration
- N37EW · registry record · serial U20602997
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Hawker Beechcraft CORP B300, built 2007
- Registration
- N545KA · registry record · serial FL-545
- Damage
- Substantial damage
- Flight
- Executive or corporate flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna TU206F preliminary · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The NTSB's narrative for the Hawker Beechcraft CORP B300 preliminary · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record for the Cessna TU206F from the NTSB's investigation tables, in plain English
What happened, in order
- Ground collision during taxi defining event
The aircraft
- Seats: 6
- Landing gear: fixed
The flight
- Runway 06/2, 5,500 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 300° at 16 knots, gusting 27
- Visibility: 10 statute miles
- Temperature: 61°F (16°C), dew point 30°F (-1°C)
- Altimeter: 30.06 inHg
- Observation at 2:00 pm from KMUT
Weather report (METAR): METAR KMUT 121955Z AUTO 30016G27KT 10SM 16/M01 A3006 RMK AO2 PWINO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
The factual record for the Hawker Beechcraft CORP B300 from the NTSB's investigation tables, in plain English
What happened, in order
- Airport occurrence during unknown defining event
The aircraft
- Seats: 19
- Landing gear: fixed
- Operator: Vette Collect Aviation LLC
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Other NTSB records under N37EW the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N37EW on the register today · the tail number may have moved to another aircraft since
- Cessna TU206 343 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- N545KA on the register today · the tail number may have moved to another aircraft since
- Muscatine Municipal · nearest airport
- Accidents and incidents in Iowa 871 since 1982 · 131 in the last ten years
- Iowa 4,514 aircraft registered
- Other NTSB records under N37EW 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/CEN26LA045.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
