Cessna 172S and Raytheon Aircraft Company B200 mid-air collision near Marathon, Florida, April 11, 2026
On April 11, 2026 at about 5:30 pm local time, 2 aircraft, Cessna 172S (N529ND) and Raytheon Aircraft Company B200 (N699BW), were involved in a mid-air collision near Marathon, Florida (The Florida Keys Marathon Intl airport). No one was hurt; 8 people were on board or involved.
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
- April 11, 2026 · about 5:30 pm local time · cases in 2026
- Place
- Marathon, Florida · The Florida Keys Marathon Intl · cases near this airport · map
- Type
- Accident · mid-air collision
- Injuries
- No one was hurt; 8 people were on board or involved.
- Weather
- not recorded
- Aircraft 1
- Cessna 172S, built 2009 · all 172Ss on the register
- Registration
- N529ND · registry record · serial 172S10981
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
- Aircraft 2
- Raytheon Aircraft Company B200, built 1999
- Registration
- N699BW · registry record · serial BB-1658
- Damage
- Substantial damage
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative for the Cessna 172S preliminary · quoted from the NTSB record
On April 11, 2026, about 1330 eastern daylight time, a Cessna 172S airplane, N529ND sustained substantial damage and a Raytheon Aircraft Company B200 (King Air) airplane, N699BW sustained minor damage when they collided in flight near Marathon, Florida. The 2 pilots aboard the Cessna and the 2 pilots and 4 passengers aboard the King Air were not injured. The Cessna was being operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight, and the King Air was being operated as Title 14 CFR Part 91 business flight. Preliminary air traffic control communications and ADS-B data provided by the FAA showed that the King Air departed Marsh Harbour (MHH), Bahamas to the southwest inbound to the Florida Keys Marathon International Airport (MTH), Marathon, Florida. About 20 nautical miles northeast of MTH, the pilot requested to cancel their instrument flight rules (IFR) flight plan to MTH. The IFR cancellation was received, and a frequency change was approved. Air traffic control informed the King Air pilots that there was traffic flying in the opposite direction at 15 miles and 5,500 ft “following the keychain.” The King Air pilots subsequently reset their transponder code from a discrete code to 1200 (the standard transponder code used by airplanes operating under visual flight rules [VFR]) as they were descending out of about 11,000 ft mean sea level (msl). The Cessna pilots reported that they were northeast bound at 5,500 ft msl, about 10 miles northwest of MTH, operating VFR with flight following. Air traffic control notified them of unknown traffic ahead at 12 o’clock and 1 mile descending out of 6,200 ft msl. Immediately after the traffic advisory, the Cessna pilot reported that “we had a midair collision,” declared an emergency, and returned to MTH for landing. The Cessna pilots stated that they had briefly observed the King Air immediately before the collision but were unable to take evasive action. The pilot advised the controller of left wing damage and control difficulties and requested emergency services upon landing. The pilot in command (PIC) of the King Air reported he was looking out the window, scanning for the traffic, when he observed the Cessna immediately before impact. He attempted evasive action; however, the left engine, wing and propeller impacted the left wing of the Cessna, which resulted in substantial damage to the Cessna’s wing and aileron. The outboard 36 inches of the Cessna’s left wing was sheared off and crumpled, with the aileron remaining partially attached, and bent aft. The King Air sustained minor damage to the left propeller, engine intake and the leading edge of the left wing. Both airplanes landed safely at MTH and were retained for further examination following the collision.
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 Raytheon Aircraft Company B200 preliminary · quoted from the NTSB record
On April 11, 2026, about 1330 eastern daylight time, a Cessna 172S airplane, N529ND sustained substantial damage and a Raytheon Aircraft Company B200 (King Air) airplane, N699BW sustained minor damage when they collided in flight near Marathon, Florida. The 2 pilots aboard the Cessna and the 2 pilots and 4 passengers aboard the King Air were not injured. The Cessna was being operated as a Title 14 Code of Federal Regulations (CFR) Part 91 instructional flight, and the King Air was being operated as Title 14 CFR Part 91 business flight. Preliminary air traffic control communications and ADS-B data provided by the FAA showed that the King Air departed Marsh Harbour (MHH), Bahamas to the southwest inbound to the Florida Keys Marathon International Airport (MTH), Marathon, Florida. About 20 nautical miles northeast of MTH, the pilot requested to cancel their instrument flight rules (IFR) flight plan to MTH. The IFR cancellation was received, and a frequency change was approved. Air traffic control informed the King Air pilots that there was traffic flying in the opposite direction at 15 miles and 5,500 ft “following the keychain.” The King Air pilots subsequently reset their transponder code from a discrete code to 1200 (the standard transponder code used by airplanes operating under visual flight rules [VFR]) as they were descending out of about 11,000 ft mean sea level (msl). The Cessna pilots reported that they were northeast bound at 5,500 ft msl, about 10 miles northwest of MTH, operating VFR with flight following. Air traffic control notified them of unknown traffic ahead at 12 o’clock and 1 mile descending out of 6,200 ft msl. Immediately after the traffic advisory, the Cessna pilot reported that “we had a midair collision,” declared an emergency, and returned to MTH for landing. The Cessna pilots stated that they had briefly observed the King Air immediately before the collision but were unable to take evasive action. The pilot advised the controller of left wing damage and control difficulties and requested emergency services upon landing. The pilot in command (PIC) of the King Air reported he was looking out the window, scanning for the traffic, when he observed the Cessna immediately before impact. He attempted evasive action; however, the left engine, wing and propeller impacted the left wing of the Cessna, which resulted in substantial damage to the Cessna’s wing and aileron. The outboard 36 inches of the Cessna’s left wing was sheared off and crumpled, with the aileron remaining partially attached, and bent aft. The King Air sustained minor damage to the left propeller, engine intake and the leading edge of the left wing. Both airplanes landed safely at MTH and were retained for further examination following the collision.
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 172S from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during enroute (cruise) defining event
The aircraft
- Seats: 4
- Landing gear: fixed
- Operator: Phoenix East Aviation LLC
The flight
- Departed from: EYM Key West FL
- Destination: HWO Hollywood FL
- A second pilot was aboard
Weather at the time
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
The factual record for the Raytheon Aircraft Company B200 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision during enroute (descent) defining event
The aircraft
- Seats: 11
- Landing gear: retractable
- Operator: Beech Transport LLC
The flight
- Departed from: MHH Marsh Harbour OF
- Destination: MTH Marathon FL
- A second pilot was aboard
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 | |||
| Passengers | 4 |
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.
Connections how this case links to the rest of the register
- N529ND on the register today · the tail number may have moved to another aircraft since
- Cessna 172 Skyhawk 20,691 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- N699BW on the register today · the tail number may have moved to another aircraft since
- Raytheon Aircraft Company 2,138 aircraft on the register
- The Florida Keys Marathon International · nearest airport
- North Perry Airport · bound for
- Accidents and incidents in Florida 6,111 since 1982 · 983 in the last ten years
- Florida 21,713 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA26LA167.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.
