FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA316 · Champion 7GCBC

5 Aug 2018 · Wiley, CO, United States

Champion 7GCBC · Accident: collision during takeoff/landing

From Southeast Colorado Regional Airport (LAA) to Wiley, CO

Report a problem

Event

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

Champion 7GCBC

Aircraft type
Champion 7
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
N90990
Operator
Unknown
Onboard fatalities
Unknown
Route
From Southeast Colorado Regional Airport (LAA), Lamar, COTo Wiley, CO
Aircraft age
About 45 years (built 1973)
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
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
Collision during takeoff/landing
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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 › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The private pilot was conducting a day visual approach to landing on his airstrip; he stated that everything seemed normal on the descent. However, he noted that the agricultural irrigation pivot sprinkler had stopped with the sprinkler's last pipe, or "overhang pipe," over the runway. The pilot thought that he was high enough to clear the sprinkler overhang pipe and had "no idea" that the airplane was not going to clear the guy-wires that supported the sprinkler overhang pipe, and the right landing gear tire struck a guy-wire that was about 10 ft higher than the sprinkler overhang pipe. The airplane's nose subsequently impacted terrain, and the airplane came to rest inverted. The pilot reported that there were no mechanical malfunctions or failures during the flight.

Probable cause

The pilot's failure to maintain proper clearance from the sprinkler guy-wire, which resulted in the airplane’s collision with the wire during a visual approach to landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA316
Event ID
20180805X21934
Case number
CEN18LA316
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: aa32b4ee7f5e4f942181224b9e04dc3754096b7cf30e1b701fa517244b1b8edf; retrieved 2026-09-16T08:03:17.699Z.