FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN12LA179 · Skeeter 1M

3 Mar 2012 · Oklahoma City, OK, United States

Skeeter 1M · Accident: loss of control in flight on approach

From Cole Landing Area Airport (2OK7) to Clarence E Page Municipal Airport (RCE)

Report a problem

Event

NTSB case
CEN12LA179
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

Skeeter 1M

Aircraft type
Skeeter 1
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
N1111V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cole Landing Area Airport (2OK7), Newcastle, OKTo Clarence E Page Municipal Airport (RCE), Oklahoma City, OK
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
Approach · VFR pattern final
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
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 pilot was flying his experimental home-built airplane on a cross-country flight when the canopy came loose, so he diverted to another airport to tighten the canopy. His airplane was on the downwind leg in the traffic pattern and another airplane was on final approach. Several witnesses said that when the accident airplane was on final approach in the traffic pattern, the pilot attempted to make a 180-degree turn. The pilot likely saw the other airplane on the runway, and, not knowing its intention, he attempted to add more space between his airplane and the other airplane. The accident airplane was observed about 400 feet above the ground in a 45-degree banked turn. The accident airplane subsequently descended and impacted terrain. The accident pilot did not have a current medical certificate. No preimpact anomalies were detected during a postaccident examination of the wreckage.

Probable cause

The pilot's failure to maintain airplane control while on final approach as he was executing a turn to provide spacing between his airplane and an airplane on the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12LA179
Event ID
20120305X03358
Case number
CEN12LA179
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. 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: 7e495a7a35d4a19c71754a4e818b643de48540914d948cf95eb5673260199a2c; retrieved 2026-09-13T22:12:56.632Z.