Raytheon Aircraft Company G36 accident near Benicia, California, September 9, 2017
On September 9, 2017 at about 9:13 pm local time, a 2006 Raytheon Aircraft Company G36, registered N7215J, was substantially damaged in an accident during initial climb near Benicia, California. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain adequate airspeed which caused the airplane to exceed its critical angle of attack and led to an aerodynamic stall.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 9, 2017 · about 9:13 pm local time
- Place
- Benicia, California · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Raytheon Aircraft Company G36 NO SERIES, built 2006
- Registration
- N7215J · no longer on the register · serial E-3715
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot and passenger departed for a personal cross-country flight. Radar data indicated that the flight track after takeoff was consistent with the course to the destination airport. During the first few minutes of flight, the radar data indicated that the airplane was in a climb. However, during the last 2 minutes of flight, as the airplane neared its level-off altitude, the airplane's speed had decreased and was approaching the stall speed, which was between 68 and 73 knots, depending on the airplane's bank. The calibrated airspeed was calculated to be about 62 knots at the last radar return. At that time, the airplane had entered a right turn and was rapidly descending. The airplane impacted terrain about 9 miles from the departure airport. Postaccident examination of the airframe and engine revealed no anomalies that would have precluded normal operation. Signatures at the accident site and the damage to the airplane indicated a near vertical impact, which was consistent with an aerodynamic stall.
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
- Aerodynamic stall/spin during initial climb defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not attained/maintained
- Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 528 hours in all; 2.7 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
Passenger
- Seat: rgt
- Injury: fatal
The aircraft
- Airframe total time: 1,535.6 hours
- Last inspection: annual inspection, December 3, 2016
- Maximum gross weight: 4,000 lb
- Landing gear: retractable
- Engine: Continental IO-550B-39B (piston); 0 hours total
The flight
- Departed from: CCR Concord CA at 9:06 pm
- Destination: ACV Arcata/Eureka CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 330° at 12 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 86°F (30°C), dew point 63°F (17°C)
- Altimeter: 29.95 inHg
- Observation at 8:53 pm from CCR, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
16 documents, released by the NTSB on September 5, 2019. 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 | Electronic Devices - Specialist's Factual Report | PDF, 4 pages | View Download |
| 2 | Flight Track Figures | PDF, 2 pages | View Download |
| 3 | On Site Examination Report | PDF, 5 pages | View Download |
| 4 | Airframe and Engine Examination Report | PDF, 6 pages | View Download |
| 5 | G36 POH Excerpt | PDF, 3 pages | View Download |
| 6 | Airplane Flight Manual Supplement - 550 | PDF, 1 page | View Download |
| 7 | Airframe Logbook Excerpt | PDF, 1 page | View Download |
| 8 | Engine Log Excerpts | PDF, 2 pages | View Download |
| 9 | Pilot Logbook Excerpts | PDF, 2 pages | View Download |
| 10 | Airplane Gross Weight Document | PDF, 2 pages | View Download |
| 11 | FAA Flying Handbook Excerpts | PDF, 2 pages | View Download |
| 12 | FAA Pilot's Handbook of Aeronautical Knowledge Excerpts | PDF, 2 pages | View Download |
| 13 | Record of Email | PDF, 1 page | View Download |
| 14 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages | View Download |
| 15 | Toxicological Report (Passenger) | PDF, 1 page | View Download |
| 16 | Toxicological Report - (Pilot) | 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.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.