Amateur-built GLASTAR accident near Cascade, Idaho, September 2, 2017
On September 2, 2017 at about 4:30 pm local time, a 1998 amateur-built GLASTAR, registered N65EW, was destroyed in an accident during maneuvering (low-alt flying) near Cascade, Idaho. It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's inadequate flight planning, preparation, and navigation, which resulted in the airplane entering a canyon that the pilot was unable to exit by climbing the airplane. Also causal were his in-flight decision-making and his execution of the course reversal turn, which resulted in an aerodynamic stall and terrain impact.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 2, 2017 · about 4:30 pm local time
- Place
- Cascade, Idaho · map
- Type
- Accident
- Injuries
- 1 person was killed and 1 person was seriously injured.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built GLASTAR GS-1, built 1998
- Registration
- N65EW · no longer on the register · serial 5296
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot, who had no mountain flying instruction, planned to fly a friend's newly-purchased experimental amateur-built airplane from Idaho to Georgia. After he took delivery of the airplane at one airport in Idaho, the pilot flew to another Idaho airport to meet his pilot-rated cousin. The next morning, the two departed in the airplane for an airstrip situated about 38 miles to the northeast, at an elevation about 5,800 ft above mean sea level (msl). The aeronautical chart of the region depicted mountainous terrain between the two airports, with peaks ranging from about 6,700 to 8,700 ft msl. While en route, the pilot entered a canyon and realized that the airplane was unable to outclimb the rising terrain. The pilot began a course reversal turn to escape the canyon, but during the turn, the airplane experienced an aerodynamic stall and impacted the ground. The airplane was destroyed, the pilot received serious injuries, and the passenger was fatally injured. The impact site was at an elevation of about 7,500 ft. The pilot's preparations for the flight were minimal, and he did not explicitly plan out the flight route or altitudes to ensure sufficient terrain clearance margins. The pilot did not reside in mountainous terrain, and had not taken any mountain-flying training courses. The pilot did not have or use any paper charts before or during the flight and did not program his intended flight route into his GPS device, which was equipped with a terrain database and terrain display and warning capability. Prior to the accident, the pilot had only accrued about 1 hour in the accident airplane make and model. After the accident, the pilot reported that he had over-estimated the airplane's climb performance. Aside from climb speeds, there was no climb performance information in the airplane Owner's Manual (OM). Because the pilot did not specify whether he used the airplane's best angle of climb airspeed for the climb, his conduct of the climb could not be evaluated, and the effect of the actual climb performance on the outcome could not be determined. Mountain flying training guidance advocates that when flying in canyons, pilots should select a flight path near the side, as opposed to the center, of the canyon in order to provide the maximum amount of terrain clearance in the event a course reversal turn becomes necessary. Because the pilot did not specify any details regarding the lateral position of the airplane before or during the course reversal turn, the pilot's execution of the turn could not be evaluated, and its effect on the outcome could not be determined. An airplane's minimum-radius turn requires use of the lowest airspeed and highest bank angle that still provide sufficient stall margin. Because the pilot did not specify the speed or bank angle that he used for his course reversal turn, the pilot's execution of the turn could not be evaluated, and its effect on the outcome could not be determined. The OM did not provide actual stall speed information, and the airplane was not equipped with a stall warning system. Because the weight, configuration, bank angle, and actual performance of the airplane were not known, the actual stall speed could not be determined. Although the pilot had deployed partial flaps at an undetermined time just prior to or during the turn in order to reduce his stall speed, that configuration change alone was insufficient to prevent the stall. Because the airplane dynamics and pilot responses were not known, the specific reason(s) for the stall were not able to be determined. The pilot's inadequate flight planning, preparation, and navigation, combined with his lack of familiarity with the airplane's performance capability, resulted in the airplane entering a canyon that the pilot was unable to exit by outclimbing the terrain. The pilot's decision to reverse course was either too late, and/or his execution of the course reversal turn was insufficient to enable successful escape from the canyon. During the course reversal turn, the airplane experienced an aerodynamic stall and impacted terrain.
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
- Preflight or dispatch event during prior to flight
- Miscellaneous/other during prior to flight
- Unknown or undetermined during enroute (cruise)
- Navigation error during enroute (cruise)
- Attempted remediation/recovery during maneuvering (low-alt flying)
- Loss of control in flight during maneuvering (low-alt flying) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Pilot
- cause Personnel issues › Task performance › Planning/preparation › Performance calculations › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Heading/course › Incorrect use/operation
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Not attained/maintained
- cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Ability to respond/compensate
- cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Awareness of condition
- cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Decision related to condition
- cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 998 hours in all; 2 in this make and model; 5 in the last 90 days; 3 in the last 30 days
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: serious injuries
Pilot-Rated Passenger
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land
- Flight time: 0 hours in all; 0 in this make and model
- Medical certificate: Class 3
- Seat: rgt
- Injury: fatal
The aircraft
- Maximum gross weight: 1,990 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: ID35 Cascade ID
- Destination: ID74 Cascade ID
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: daylight
- Temperature: 66°F (19°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on July 15, 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 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Accident Location | PDF, 1 page | View Download |
| 3 | Record of Conversation - (Pilot) | PDF, 1 page | View Download |
| 4 | Record of Conversation (New Owner) | PDF, 2 pages | View Download |
| 5 | Record of Conversation (Previous Owner Sept 6) | PDF, 2 pages | View Download |
| 6 | Record of Conversation (Previous Owner Sept 7) | PDF, 2 pages | View Download |
| 7 | Record of Conversation (Fuel) | PDF, 1 page | View Download |
| 8 | radar Search Results Email | PDF, 1 page | View Download |
| 9 | Owner's Manual Excerpts | PDF, 9 pages | View Download |
| 10 | Photographs | PDF, 5 pages | 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.
