FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA202 · Harry Oas Pitts S1C

29 May 2016 · Carlsbad, NM, United States

Harry Oas Pitts S1C · Accident: loss of control on ground during landing

From Big Spring Mc Mahon-Wrinkle Airport (BPG) to Cavern City Air Terminal (CNM)

Report a problem

Event

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

Harry Oas Pitts S1C

Aircraft type
Harry Oas PITTS S1C
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
N95R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Big Spring Mc Mahon-Wrinkle Airport (BPG), Big Spring, TXTo Cavern City Air Terminal (CNM), Carlsbad, NM
Aircraft age
About 49 years (built 1967)
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
  • Environmental issues › Conditions/weather/phenomena

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot was landing the tailwheel-equipped airplane; it departed the left side of the runway during the landing roll and subsequently nosed over. A skid mark associated with the left main wheel was observed on the runway following the accident. A postaccident examination did not reveal any anomalies of the brake system. Left and right rudder/brake pedal travel was not restricted, and the brake system was intact and operational. Weather information indicated that there was a 20° right crosswind at 8 knots about the time of the accident. Given the absence of mechanical anomalies, it is likely that the pilot failed to maintain directional control during the landing roll.

Probable cause

The pilot's failure to maintain directional control while landing in crosswind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA202
Event ID
20160601X13049
Case number
CEN16LA202
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: 944012a37f3c591dd4dcc32bf45910268417dee4cb6d8c829475f34f3f405297; retrieved 2026-09-16T03:26:55.306Z.