20251112016532A

Accident · Substantial damage

FAA accident report · Cessna TU206F · Muscatine, IA · November 12, 2025

Date
November 12, 2025 · 14:05 local
Place
Muscatine, IA
Airport
Muscatine Municipal
Phase of flight
Taxi
Operating rules
General operating rules (Part 91)
Collision
Collision on the ground
Damage
Substantial damage
Aircraft
N37EW
NTSB investigation
NTSBCEN26LA045
Reported as
Cessna TU206F
Reported engine
Continental TSIO-520 series
People aboard
2
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Commercial pilot, private pilot, student
Pilot’s flight hours
570 total472 in this make and model63 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

On November 12, 2025, at approximately 1400 local time, an incident occurred at Muscatine Municipal Airport (mut) involving a Cessna 206 and a king air. The weather was clear and sunny with unrestricted visibility, with winds from 300 degrees at 17 knots, gusting to 25 knots. After refueling, the Cessna attempted to taxi to runway 30. A witness stated that the Cessna pilot communicated his intentions over the radio to taxi to runway 30. Prior to this, the king air had announced its position on the ILS for runway 24 during final approach. The Cessna taxied out and crossed runway 24, where it was struck by the king air that had landed. The collision resulted in substantial damage to both aircraft, with the king air's right wing severely damaging the Cessna's tail.

The investigation began with interviews of the king air pilot and co-pilot, who was the check pilot, as well as the aviation safety inspector (ASI) who was in the back evaluating the check pilot. The inspector verified that the ASI was current to conduct the checkride for the check pilot. The inspector then contacted the airport manager, who had a video of the accident, and also interviewed a witness who had overheard the radio communications. Following this, the inspector spoke with the Cessna pilot to obtain his statement. All the pilots provided written statements and emailed them to the inspector.

The investigation included a review of pilot records for both the Cessna and king air crews, confirming that all were current and legally qualified to fly. Additionally, the aircraft logs were reviewed, confirming that both aircraft were airworthy for the flights that day.

The director of operations for the part 135 king air company met with the inspector at the location. Together, they examined the aircraft, which had been moved to a hangar, and also inspected the runway. The inspector took photographs of the skid marks on the runway to verify their consistency with the pilots' statements. The Cessna pilot stated that the accident happened around 1405 local time, and after ensuring everyone was okay in both aircraft, they notified the FAA around 1410. The springfield FSDO was notified approximately at 1500 or shortly after, and the inspector was notified at 1550 on November 12, 2025.

As the FAA filed it

ON NOVEMBER 12, 2025, AT APPROXIMATELY 1400 LOCAL TIME, AN INCIDENT OCCURRED AT MUSCATINE MUNICIPAL AIRPORT (MUT) INVOLVING A CESSNA 206 AND A KING AIR. THE WEATHER WAS CLEAR AND SUNNY WITH UNRESTRICTED VISIBILITY, WITH WINDS FROM 300 DEGREES AT 17 KNOTS, GUSTING TO 25 KNOTS. AFTER REFUELING, THE CESSNA ATTEMPTED TO TAXI TO RUNWAY 30. A WITNESS STATED THAT THE CESSNA PILOT COMMUNICATED HIS INTENTIONS OVER THE RADIO TO TAXI TO RUNWAY 30. PRIOR TO THIS, THE KING AIR HAD ANNOUNCED ITS POSITION ON THE ILS FOR RUNWAY 24 DURING FINAL APPROACH. THE CESSNA TAXIED OUT AND CROSSED RUNWAY 24, WHERE IT WAS STRUCK BY THE KING AIR THAT HAD LANDED. THE COLLISION RESULTED IN SUBSTANTIAL DAMAGE TO BOTH AIRCRAFT, WITH THE KING AIR'S RIGHT WING SEVERELY DAMAGING THE CESSNA'S TAIL.

THE INVESTIGATION BEGAN WITH INTERVIEWS OF THE KING AIR PILOT AND CO-PILOT, WHO WAS THE CHECK PILOT, AS WELL AS THE AVIATION SAFETY INSPECTOR (ASI) WHO WAS IN THE BACK EVALUATING THE CHECK PILOT. THE INSPECTOR VERIFIED THAT THE ASI WAS CURRENT TO CONDUCT THE CHECKRIDE FOR THE CHECK PILOT. THE INSPECTOR THEN CONTACTED THE AIRPORT MANAGER, WHO HAD A VIDEO OF THE ACCIDENT, AND ALSO INTERVIEWED A WITNESS WHO HAD OVERHEARD THE RADIO COMMUNICATIONS. FOLLOWING THIS, THE INSPECTOR SPOKE WITH THE CESSNA PILOT TO OBTAIN HIS STATEMENT. ALL THE PILOTS PROVIDED WRITTEN STATEMENTS AND EMAILED THEM TO THE INSPECTOR.

THE INVESTIGATION INCLUDED A REVIEW OF PILOT RECORDS FOR BOTH THE CESSNA AND KING AIR CREWS, CONFIRMING THAT ALL WERE CURRENT AND LEGALLY QUALIFIED TO FLY. ADDITIONALLY, THE AIRCRAFT LOGS WERE REVIEWED, CONFIRMING THAT BOTH AIRCRAFT WERE AIRWORTHY FOR THE FLIGHTS THAT DAY.

THE DIRECTOR OF OPERATIONS FOR THE PART 135 KING AIR COMPANY MET WITH THE INSPECTOR AT THE LOCATION. TOGETHER, THEY EXAMINED THE AIRCRAFT, WHICH HAD BEEN MOVED TO A HANGAR, AND ALSO INSPECTED THE RUNWAY. THE INSPECTOR TOOK PHOTOGRAPHS OF THE SKID MARKS ON THE RUNWAY TO VERIFY THEIR CONSISTENCY WITH THE PILOTS' STATEMENTS. THE CESSNA PILOT STATED THAT THE ACCIDENT HAPPENED AROUND 1405 LOCAL TIME, AND AFTER ENSURING EVERYONE WAS OKAY IN BOTH AIRCRAFT, THEY NOTIFIED THE FAA AROUND 1410. THE SPRINGFIELD FSDO WAS NOTIFIED APPROXIMATELY AT 1500 OR SHORTLY AFTER, AND THE INSPECTOR WAS NOTIFIED AT 1550 ON NOVEMBER 12, 2025.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other aircraft in the event · 1

Each aircraft in a collision has its own report.

Other reports on N37EW · 1

Matched to the same aircraft by N-number and date.