FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21LA161 · Rans S12

17 Apr 2021 · Colville, WA, United States

Rans S12 · Accident: aerodynamic stall/spin while maneuvering

From Colville Municipal Airport (63S) to Colville Municipal Airport (63S)

Report a problem

Event

NTSB case
WPR21LA161
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
2 · 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

Rans S12

Aircraft type
Rans S12
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
N707PH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Colville Municipal Airport (63S), Colville, WATo Colville Municipal Airport (63S), Colville, WA
Aircraft age
About 26 years (built 1995)
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
Maneuvering · low-altitude flying
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
Aerodynamic stall/spin
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The owner of the airplane, who was not a pilot, was selling the airplane to his friend, who was a pilot. The two spent the winter rebuilding the airplane, which had previously been involved in an accident and had been in storage, in pieces, for the previous 5 years. On the day of the accident, the pilot announced to an acquaintance that the airplane’s maintenance issues had been corrected and they were going to take the airplane on a test flight. A witness who saw the airplane’s takeoff and initial climb reported that the airplane’s climb rate was “not impressive” and that it was only “slightly climbing.” Two witnesses who saw the airplane before the accident stated that the engine was “sputtering” and that the airplane was “losing altitude quickly.” Photos of the airplane just before the accident showed the airplane flying toward a set of power distribution lines before entering a steep bank away from the lines, after which the airplane impacted terrain. The airplane came to rest in a nose-down attitude in an open field adjacent to the power distribution lines. Examination of the wreckage revealed that both carburetors’ float brackets were not adjusted in accordance with the manufacturer’s maintenance manual, which likely restricted the amount of fuel in the carburetor bowls. Multiple people stated that the owner and pilot had been troubleshooting a carburetor issue before the accident flight. One person described it as, “over-producing fuel, and the fuel was running out of the back [of the airplane].” The repair work on the airplane was overseen by a mechanic with inspection authorization who advised the two as they went and gave the two general maintenance advice. The mechanic was aware that neither the owner nor the pilot were certificated mechanics or light sport repairmen; however, he described the owner as a competent mechanic. About 1 month before the accident, the mechanic completed an entry in the airplane’s maintenance logbook stating that the condition inspection had been completed and that the airplane was “found to be in an airworthy condition” and “approved for return to service.” The mechanic was aware of the carburetor issue but did not know who worked on the carburetors and thought that the carburetors had been sent away for repair. After the carburetors were reinstalled, the mechanic observed the pilot conduct ground runs and thought that the engine “sounded fine.” It is likely that the engine was not producing full power as a result of the improperly adjusted carburetor float brackets, which resulted in degraded climb performance or the airplane’s inability to climb. Based on the witness statements and photos, it is likely that the pilot was maneuvering to avoid powerlines when he exceeded the airplane’s critical angle of attack and the airplane entered an aerodynamic stall.

Probable cause

The pilot’s exceedance of the airplane’s critical angle of attack while maneuvering to avoid powerlines, which resulted in an aerodynamic stall and a loss of control. Contributing to the accident was the partial loss of engine power due to improper maintenance of the carburetors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21LA161
Event ID
20210418102927
Case number
WPR21LA161
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, cause areas. 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: 1f07f4e3f4a5f52b43ee412a58267fccfb99928e42621336df465cb542e268a4; retrieved 2026-09-15T07:26:59.262Z.