SEA93LA169 · Hadaller MURPHY RENEGADE MURPHY REN
Hadaller MURPHY RENEGADE MURPHY REN · Accident: forced landing
From 7V6 to Sheridan County Airport (SHR)
Event
- NTSB case
- SEA93LA169
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Hadaller MURPHY RENEGADE MURPHY REN
- Aircraft type
- Hadaller MURPHY RENEGADE
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N95HH
- Operator
- Hadaller, Harold L. · private individual
- Onboard fatalities
- Unknown
- Route
- From 7V6To Sheridan County Airport (SHR), Sheridan, WY
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Other
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Forced landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT AFTER A NORMAL TAKEOFF, THE AIRPLANE WAS NOT CAPABLE OF OUT CLIMBING THE RISING TERRAIN. THERE WAS NOT ENOUGH SPACE TO REVERSE COURSE, SO HE ELECTED TO MAKE AN EMERGENCY LANDING ON THE AVAILABLE TERRAIN. WHILE LANDING ON ROUGH TERRAIN, THE AIRPLANE NOSED OVER. THE PILOT REPORTED THAT HE WAS AWARE OF THE HIGH DENSITY ALTITUDE, BUT BECAUSE ANOTHER AIRPLANE HAD TAKEN OFF BEFORE HIS FLIGHT WITHOUT ANY DIFFICULTY, HE FELT THAT HIS AIRPLANE WOULD CLIMB AND CLEAR THE TERRAIN. PERFORMANCE DATA ON THE HOMEBUILT AIRPLANE WAS LIMITED, AND THE PILOT WAS NOT SURE OF ITS CAPABILITY. ELEVATION AT THE ACCIDENT SITE WAS ABOUT 4000 FEET AND THE TEMPERATURE WAS 103 DEGREES. DENSITY ALTITUDE WAS CALCULATED TO BE ABOUT 8500 FEET.
Probable cause
IMPROPER PLANNING/DECISION BY THE PILOT. FACTORS RELATED TO THE ACCIDENT WERE: RISING/MOUNTAINOUS TERRAIN, HIGH DENSITY ALTITUDE, THE LACK OF CLIMB PERFORMANCE INFORMATION AVAILABLE TO THE PILOT, AND ROUGH/UNEVEN TERRAIN IN THE EMERGENCY LANDING AREA.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA93LA169
- Event ID
- 20001211X13261
- Case number
- SEA93LA169
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ef0b113496c555adb8e5754c7e5fc68fc7fd75cef31cc19a2cc4f609d00fe1f8; retrieved 2026-09-23T01:48:12.023Z.