FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA471 · Piper PA28 235

31 Jul 2019 · Falcon, CO, United States

Piper PA28 235 · Accident: landing area undershoot

From City of Colorado Springs Municipal Airport (COS) to Meadow Lake Airport (FLY)

Report a problem

Event

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

Piper PA28 235

Aircraft type
Piper PA28
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
N8641W
Operator
Unknown
Onboard fatalities
Unknown
Route
From City of Colorado Springs Municipal Airport (COS), Colorado Springs, COTo Meadow Lake Airport (FLY), Falcon, CO
Aircraft age
About 56 years (built 1963)
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
Landing area undershoot
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 › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot reported that the main runway was closed at the airport, so he planned to make a short-field landing on a perpendicular 2,084-ft-long runway (runway 8). During landing, the airplane "ended up short," and he attempted to go around, but he did not add power fast enough. The airplane impacted a construction barrier near the runway threshold, and the left main landing gear separated. The airplane sustained substantial damage to the left horizontal stabilizer and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Archived NOTAMs for the date of the accident stated the following: RWY 15/33 CLSD; RWY 08 CLSD TO LDG; RWY 26 CLSD EXC FSL. The airport manager reported that runway 15/33 was closed due to construction and that they issued a NOTAM with the intention that pilots could take off on runway 8 and conduct only full-stop landings on runway 26 to avoid construction equipment.

Probable cause

The pilot's failure to maintain a proper approach path and his delayed decision to go around, which resulted in impact with a construction barrier before the runway. Contributing to the accident was the pilot's decision to land on a runway closed for landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA471
Event ID
20190731X80756
Case number
GAA19CA471
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
  • 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: bbd499b6e2f11f8229765f42aadf79441ec6bcda6c8a357ad5a23215ef3125e5; retrieved 2026-09-16T09:37:31.421Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: departure. COS is Colorado Springs Municipal Airport at Colorado Springs, CO; the city name is missing its final s.