CEN22FA029 · Vans RV 6
Vans RV 6 · Accident: loss of control in flight en route
From Oakland County International Airport (PTK) to William B Bolton Airport (Y87)
Event
- NTSB case
- CEN22FA029
- 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
- 1 · 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
Vans RV 6
- Aircraft type
- Vans RV
- 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
- N16TG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Oakland County International Airport (PTK), Pontiac, MITo William B Bolton Airport (Y87), Empire, MI
- Aircraft age
- About 18 years (built 2003)
- 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
- En route · cruise
- 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 in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
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
Flight track data indicated that the airplane was on a cross-country flight in level cruise flight until track data were lost. The airplane impacted the back yard of a residence. Impact signatures indicated a 45° nose-low impact angle, consistent with an aerodynamic stall. The airplane’s wood core propeller was not splintered, indicating low or no engine power at impact. Examination of the airframe, engine, and related systems did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operations.
The accident site was located about 7.3 nautical miles (nm) to the east of the last recorded track and about 1 nm south of the approach end of an airport runway. The location of the accident site suggests that the pilot had diverted from his original course and was attempting to land at the nearby airport. The loss of automatic dependent surveillance-broadcast (ADS-B) flight track data and discrete radar beacon returns indicated an interruption of transmission of the data from the airplane.
Based on the available information, it is likely that the pilot was diverting to the airport near the accident site. The pilot had been in communication with air traffic control, but no distress calls were received. This along with the interruption of ADS-B track data and discrete radar beacon returns suggest a possible interruption in airplane electrical power. However, loss of electrical power would not explain the lack of engine power at impact since one of the ignition systems could operate independently without aircraft electrical power.
Additionally, the distance from the final radar return to the accident site was not consistent with the achievable glide ratio of the airplane, suggesting that the engine did not lose power at the point where the final discrete beacon return was received. Therefore, the reason the airplane was diverting to the alternate airport could not be determined. The impact signatures indicated that the pilot likely failed to maintain the proper airspeed, leading to an exceedance of the airplane’s critical angle of attack and subsequent aerodynamic stall and loss of airplane control.
Based upon the results from the toxicology, the pilot likely had taken allergy, cold, or sleep-aid medications. However, pilot performance does not appear to be an issue. Thus, while diphenhydramine was detected during the toxicology, it is unlikely that the effects from the pilot’s use of diphenhydramine contributed to this accident.
Probable cause
The pilot’s failure to maintain adequate airspeed and exceedance of the airplane’s critical angle of attack during landing approach, which resulted in an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA029
- Event ID
- 20211105104207
- Case number
- CEN22FA029
- 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, 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: f9e5425219c30a60aacb1799300e96a1b414011f410d48963d518ad3261db19e; retrieved 2026-09-15T07:36:51.583Z.