Beech J35 and Beech M35 mid-air collision near Fredericksburg, Texas, November 6, 2020
On November 6, 2020 at about 10:38 pm local time, 2 aircraft, Beech J35 (N617Q) and Beech M35 (N338Z), were involved in a mid-air collision near Fredericksburg, Texas. 1 person was killed and 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot of the J35’s failure to maintain clearance from the M35, which resulted in a midair collision and the J35 pilot’s subsequent loss of control and impact with terrain.
The pilot of the J35’s failure to maintain clearance from the M35, which resulted in a midair collision and the J35 pilot’s subsequent loss of control and impact with terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 6, 2020 · about 10:38 pm local time · cases in 2020
- Place
- Fredericksburg, Texas · map
- Type
- Accident · mid-air collision
- Injuries
- 1 person was killed and 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Beech J35, built 1958 · all J35s on the register
- Registration
- N617Q · no longer on the register · serial D-570
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
- Aircraft 2
- Beech M35, built 1960 · all M35s on the register
- Registration
- N338Z · no longer on the register · serial D-6506
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative for the Beech J35 final · quoted from the NTSB record
The accident flight was a planned four-airplane formation practice flight. A Beech J35 was the flight leader and departed first along with a Beech M35. The third and fourth airplanes departed shortly thereafter. After takeoff, the M35’s landing gear would not retract, and the M35 moved to the “route” position (about 3 to 4 airplane widths away from the J35) to troubleshoot the landing gear problem. The third and fourth airplanes departed the formation, and the pilot of the J35 directed the pilot of the M35 to take the lead position back to the airport. While on downwind before turning onto the base leg, the pilot and observer of the M35 heard a loud “bang/wham,” and the airplane violently shook. The M35’s propeller assembly separated from the airplane and the pilot performed a forced landing. The airplane sustained substantial damage to its fuselage and left wing. The J35 entered an uncontrolled descent, impacted terrain, and was destroyed by postimpact fire. Postaccident examination of the airplanes revealed that the J35’s propeller contacted the left forward side of the M35. Evidence of propeller contact was noted on the M35 engine, engine cowling, and nose wheel tire. Both airplanes were operating in the same landing gear and flap configurations at the time of the collision. A performance study showed that, about one second before the collision, the M35’s descent rate increased from 350 ft/min to 750 ft/min. Based on the available information, the accident is consistent with the J35 pilot’s failure to maintain separation from the M35 while maneuvering.
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 Beech M35 final · quoted from the NTSB record
The accident flight was a planned four-airplane formation practice flight. A Beech J35 was the flight leader and departed first along with a Beech M35. The third and fourth airplanes departed shortly thereafter. After takeoff, the M35’s landing gear would not retract, and the M35 moved to the “route” position (about 3 to 4 airplane widths away from the J35) to troubleshoot the landing gear problem. The third and fourth airplanes departed the formation, and the pilot of the J35 directed the pilot of the M35 to take the lead position back to the airport. While on downwind before turning onto the base leg, the pilot and observer of the M35 heard a loud “bang/wham,” and the airplane violently shook. The M35’s propeller assembly separated from the airplane and the pilot performed a forced landing. The airplane sustained substantial damage to its fuselage and left wing. The J35 entered an uncontrolled descent, impacted terrain, and was destroyed by postimpact fire. Postaccident examination of the airplanes revealed that the J35’s propeller contacted the left forward side of the M35. Evidence of propeller contact was noted on the M35 engine, engine cowling, and nose wheel tire. Both airplanes were operating in the same landing gear and flap configurations at the time of the collision. A performance study showed that, about one second before the collision, the M35’s descent rate increased from 350 ft/min to 750 ft/min. Based on the available information, the accident is consistent with the J35 pilot’s failure to maintain separation from the M35 while maneuvering.
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 Beech J35 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision defining event
The NTSB's findings
- Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Heading/course › Not attained/maintained
- Personnel issues › Physical › Sensory ability/limitation › Visual function › Pilot
Pilot
- Certificate: airline transport pilot, flight instructor, flight engineer
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 23,000 hours in all
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Last inspection: inspection type not recorded
- Maximum gross weight: 2,900 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental IO-550B (piston); 0 hours total
- Fire on the ground
The flight
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 150° at 7 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 73°F (23°C), dew point 54°F (12°C)
- Altimeter: 30.06 inHg
- Observation at 4:35 pm from KT82, 2 miles away
Weather report (METAR): KT82 062235Z AUTO 15007KT 10SM SCT070 23/12 A3006 RMK AO2 T02320124
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
The factual record for the Beech M35 from the NTSB's investigation tables, in plain English
What happened, in order
- Midair collision defining event
The NTSB's findings
- Personnel issues › Physical › Sensory ability/limitation › Visual function › Pilot
Pilot
- Certificate: airline transport pilot, flight instructor, flight engineer
- Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instrument: airplane; rotorcraft: glider
- Flight time: 28,000 hours in all; 600 in this make and model; 21,000 as pilot in command; 1,000 on instruments
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: left
- Injury: no injuries
Pilot-Rated Passenger
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,467 hours in all
- Last flight review: September 13, 2020
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: rgt
- Injury: minor injuries
The aircraft
- Airframe total time: 4,343.0 hours
- Last inspection: annual inspection, June 10, 2020; 10 hours since
- Maximum gross weight: 2,950 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental IO-520-BB (piston); 740 hours total
The flight
- Flight plan: none
- A second pilot was aboard
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Photographs from the investigation 6 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – N617Q Main Wreckage
Photo 2 – N617Q Engine and Propeller
Photo 3 – N338Z Main Wreckage
Photo 4 – N338Z Engine Cowling Damage
Photo 5 – N338Z Nose Wheel Tire
Photo 6 – N338Z Propeller AssemblyThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on April 22, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
Connections how this case links to the rest of the register
- N617Q: not on the register today · the record of its deregistration
- Beechcraft J35 221 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- N338Z: not on the register today · the record of its deregistration
- Beechcraft M35 225 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Continental IO-550B 375 aircraft carry this series today · as the NTSB recorded it
- Engine: Continental IO-520-BB 44 aircraft carry this series today · as the NTSB recorded it
- Accidents and incidents in Texas 6,244 since 1982 · 1,061 in the last ten years
- Texas 29,985 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN21FA043.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.
