Hawker Beechcraft CORP G36 accident near Danbury, Connecticut, June 4, 2026
On June 4, 2026 at about 2:18 pm local time, a 2010 Hawker Beechcraft CORP G36, registered N726EA, was substantially damaged in an accident during takeoff (rejected takeoff) near Danbury, Connecticut (Danbury Muni airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 4, 2026 · about 2:18 pm local time · cases in 2026
- Place
- Danbury, Connecticut · Danbury Muni · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Hawker Beechcraft CORP G36, built 2010
- Registration
- N726EA · registry record · serial E-3943
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot planned to conduct a post-maintenance test flight in the vicinity of the departure airport. The pilot initially reported that the takeoff seemed normal at first, but as it progressed it began to feel “sluggish.” When the airplane was about half to three-quarters of the way down the runway, he observed an indicated airspeed of 62 knots, and became concerned the airplane was not performing correctly. He elected to abort the takeoff, retarded the throttle and applied brakes. The airplane continued past the end of the runway, veered into grass, and impacted a perimeter fence, which resulted in substantial damage to the airplane’s left wing. A review of recovered data recorded by the onboard avionics showed that the airplane accelerated to an indicated airspeed of 85 knots before it began decelerating. The pilot, after reviewing the recorded avionics data, acknowledged that the engine developed full rated power throughout the takeoff roll, and that the airplane accelerated normally prior to the abort decision. He also reported that there was no glare that would have impacted his ability to observe the primary flight display’s airspeed indicator. The pilot also stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
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 from the NTSB's investigation tables, in plain English
What happened, in order
- Runway excursion during takeoff (rejected takeoff) defining event
- Attempted remediation/recovery during takeoff
The NTSB's findings
- Personnel issues › Action/decision › Action › Unnecessary action › Pilot
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 972 hours in all; 450 in this make and model; 0.1 in the last 90 days; 0.1 in the last 30 days; 734.4 as pilot in command
- Last flight review: May 21, 2026
- Medical certificate: BasicMed (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 462.4 hours
- Last inspection: annual inspection, January 5, 2026; 0 hours since
- Maximum gross weight: 3,650 lb
- Seats: 6
- Landing gear: retractable
- Engine: Continental IO 550 B39B (piston); 462 hours total
The flight
- Departed from: DXR Danbury CT at 2:17 pm
- Flight plan: none
- Runway 35, 3,135 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 080° at 4 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 75°F (24°C), dew point 52°F (11°C)
- Altimeter: 30.18 inHg
- Observation at 9:53 am from DXR
Weather report (METAR): METAR KDXR 041353Z 08004KT 10SM CLR 24/11 A3018 RMK AO2 SLP215 T02440111
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Accident Airplane (N727EA) Impacted Perimeter Fence
Photograph 2 – Left Wing Leading Edge Damage
Photograph 3 – Left Wing Lower Surface Torn Skin and Flap
Photograph 4 – Left Aileron and Flap DamageThe 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
6 documents, released by the NTSB on August 20, 2026. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | FAA Interview of Pilot | PDF, 2 pages | View Download |
| 3 | Memorandum of Record - Pilot Follow-up Questions | PDF, 2 pages | View Download |
| 4 | Investigation Photos | PDF, 5 pages · our copy | View Download |
| 5 | G1000 Recorded Data | data file | Download |
| 6 | Evidence Control Form | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N726EA on the register today · the tail number may have moved to another aircraft since
- Engine: Continental IO 550 B39B 3,077 aircraft carry this series today · as the NTSB recorded it
- Danbury Municipal · nearest airport
- Accidents and incidents in Connecticut 522 since 1982 · 68 in the last ten years
- Connecticut 1,613 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA26LA229.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.
