Boeing E75 accident near Bozeman, Montana, July 14, 2013
On July 14, 2013 at about 3:30 pm local time, a Boeing E75, registered N5176N, was substantially damaged in an accident during initial climb near Bozeman, Montana (Bozeman Yellowstone airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s failure to maintain adequate airspeed during a turn, which resulted in a loss of lift and collision with terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 14, 2013 · about 3:30 pm local time · cases in 2013
- Place
- Bozeman, Montana · Bozeman Yellowstone · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Boeing E75 · all E75s on the register
- Registration
- N5176N · registry record · serial 75-5379
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that he and the pilot-rated passenger, departed from the turf runway in calm wind conditions. During the initial climb, the airplane’s climb rate was not as expected and he attributed this degraded climb performance to likely being the result of the addition of the passenger’s weight. Upon reaching 200 feet above ground level (agl), the pilot began a 180-degree turn to the north in an effort to gain altitude while avoiding maneuvering over obstacles and a more densely populated area. As the airplane entered the bank, the pilot felt a degradation in performance despite indications that both the engine power and airspeed were adequate. The airplane was not maintaining altitude and in an effort to avoid colliding into a subdivision, the pilot increased the bank angle. The airplane subsequently collided into terrain and came to rest in a ditch adjacent to the airport’s perimeter fence. During the accident sequence the airplane sustained damage to the wings and empennage. The pilot further stated that he believed the airplane’s descent during the turn was a result of either of the following: a downdraft, too high angle-of-attack attitude, or possible decrease in engine power output. He reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The passenger opined that the accident was a result of the airspeed being too slow for the steep bank angle.
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
- Loss of lift during initial climb defining event
- Loss of control in flight during initial climb
- Collision with terrain or object (not controlled flight into terrain) during initial climb
The NTSB's findings
- 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
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; rotorcraft: glider
- Flight time: 1,780 hours in all; 611 in this make and model
- Medical certificate: Class 3 (with waivers/limitations)
- Injury: no injuries
The aircraft
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming R680 (piston); 0 hours total
The flight
- Departed from: BZM Bozeman MT at 3:30 pm
- Destination: BZM Bozeman MT
- Flight plan: not recorded
- Runway 11, 3,197 ft by 80 ft
Weather at the time
- Light: daylight
- Visibility: 15 statute miles
- Sky: clear
- Temperature: 64°F (18°C), dew point 48°F (9°C)
- Altimeter: 30.21 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on September 10, 2013. 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, 13 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N5176N the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N5176N on the register today · the tail number may have moved to another aircraft since
- Boeing E75 Stearman Kaydet 343 registered today · the model family and its accident history
- Boeing 6,679 aircraft on the register
- Engine: Lycoming R680 219 aircraft carry this series today · as the NTSB recorded it
- Accidents and incidents in Montana 1,121 since 1982 · 166 in the last ten years
- Montana 6,041 aircraft registered
- Other NTSB records under N5176N 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/WPR13CA325.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.
