FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA15CA132 · Ervin REX H BEAR HAWK

21 Jun 2015 · Merrill, OR, United States

Ervin REX H BEAR HAWK · Accident: loss of control on ground during landing

From Johnson Creek Airport (3U2) to Klamath Falls, OR (no airport)

Report a problem

Event

NTSB case
GAA15CA132
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
Unknown
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

Ervin REX H BEAR HAWK

Aircraft type
Ervin Rex BEAR HAWK
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
N939RE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Johnson Creek Airport (3U2), YELLOW PINE, IDTo Klamath Falls, OR (no airport)
Aircraft age
Built the same year (2015)
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
Landing · landing roll
Defining eventThe 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
Loss of control on ground
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot, while on approach to a private grass air strip he observed the midfield wind sock indicating light and variable winds. After a normal approach and touch down, during the landing roll he encountered a strong crosswind from the right. Subsequently, the airplane began to swerve and then entered a ground loop to the left. During the ground loop, the right wing impacted the runway and the airplane came to rest. The pilot reported that after he exited the airplane, he observed a quartering tailwind at 15 miles per hour.

The pilot stated there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The right wing and elevator were substantially damaged in the accident. The reported winds at an airport 5 nautical miles away about the time of the accident were from a variable direction at 3 knots.

Probable cause

The pilot's failure to maintain directional control during landing, which resulted in a ground loop.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA15CA132
Event ID
20150623X50951
Case number
GAA15CA132
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. 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: d512460b97a890f1cb93c4cc070495ae34092fe2cf39b9d1a85f17cfccd24c5c; retrieved 2026-09-16T02:27:06.049Z.