FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA386 · Black Christopher SPARROW SPORT SPEC

19 Jul 2014 · Moriarty, NM, United States

Black Christopher SPARROW SPORT SPEC · Accident: abnormal runway contact during landing

From Moriarty Municipal Airport (0E0) to Mid Valley Airpark (E98)

Report a problem

Event

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

Black Christopher SPARROW SPORT SPEC

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
N41475
Operator
Zaytsev Petr
Onboard fatalities
Unknown
Route
From Moriarty Municipal Airport (0E0), Moriarty, NMTo Mid Valley Airpark (E98), Los Lunas, NM
Aircraft age
About 10 years (built 2004)
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
Abnormal runway contact
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

Following an intermediate fuel stop, the pilot reported that the engine began to overheat during the takeoff climb. The pilot entered a left pattern to land back at the airport. During the landing, the wind was from 60 degrees right of the runway heading at 18 knots gusting to 23 knots. When the airplane landed on the runway, the pilot could not compensate for the crosswind and the right wing lifted up and the airplane began to roll left. While slowing during the landing roll, the left main landing gear broke and the left wingtip contacted the runway. The airplane then nosed over and came to rest. Substantial damage was sustained to the wings and vertical stabilizer. The pilot reported that the number two cylinder overheated due to its operation at a high temperature of 91 degrees Fahrenheit and density altitude of over 9,400 feet. No other anomalies were detected with the airframe and engine. Another runway was available at the airport which would place the wind 40 degrees left of runway heading that would have reduced the crosswind component.

Probable cause

The pilot's loss of directional control while landing in gusty crosswind conditions. Contributing to the accident was the pilot's operation of the engine above its normal temperature limit on takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA386
Event ID
20140722X62841
Case number
CEN14CA386
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2014-07-20.
  • API snapshot SHA-256: 4d6e092fa7b903afebe77da90d1794755a204f8eda33aa94d889bf15574e9dd5; retrieved 2026-09-16T00:57:38.938Z.