FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN86FA149 · American AA-1 YANKEE AA-1 YANKE

4 Jun 1986 · Cheyenne, WY, United States

American AA-1 YANKEE AA-1 YANKE · Accident: in flight collision with terrain/water during initial climb

From Cheyenne Regional Jerry Olson Field (CYS) to 3V3 · Flagler, CO

Report a problem

Event

NTSB case
DEN86FA149
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
0
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

American AA-1 YANKEE AA-1 YANKE

Aircraft type
American AA-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
N5935L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cheyenne Regional Jerry Olson Field (CYS), Cheyenne, WYTo 3V3 · Flagler, CO
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
Initial climb
First occurrenceThe 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
In flight collision with terrain/water
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

  • Pilot in command › Aircraft weight and balance, exceeded
  • Pilot in command › Mixture, improper

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

NTSB narrative

DURING TAKEOFF ON A 4,997 FOOT LONG RWY, THE ACFT BECAME AIRBORNE, SETTLED BACK ONTO THE RWY AND LIFTED OFF AGAIN JUST PRIOR TO REACHING THE END OF THE RWY. AFTER TAKEOFF THE PLT WAS NOT ABLE TO MAINTAIN FLT. THE ACFT IMPACTED ON A STREET, TRAVELED 30 FEET, STRUCK A WOODEN FENCE AND CAME TO REST AGAINST A TREE ON THE FRONT LAWN OF A PRIVATE RESIDENCE. MOST OF THE PLT'S FLT EXPERIENCE WAS IN AREAS WITH ELEVATIONS NEAR SEA LEVEL. HE STATED HE WAS NOT AWARE THE MIXTURE SHOULD BE LEANED DURING TAKEOFF FROM HIGH ALT ARPTS AS THE ACFT OWNER MANUAL SUGGESTS. CHEYENNE ARPT ELEVATION IS 6,150 FT MSL. THE ACFT WAS ALSO DETERMINED TO HAVE BEEN 35 LBS OVER MAX GROSS WEIGHT AT TAKEOFF.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record DEN86FA149
Event ID
20001213X33818
Case number
DEN86FA149
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 910a94c698b8a03d1ee9ea1e53d2848599d218bf3bbabfbbc0dcbef7ef64c276; retrieved 2026-09-21T16:57:37.850Z.