# NTSB GAA19CA471: Piper PA28, N8641W, Falcon, CO, July 31, 2019 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 31, 2019 - Place: Falcon, CO - Coordinates: 38.943611, -104.570274 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.9436&lon=-104.5703&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report April 13, 2020 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 99974 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA19CA471 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/99974/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=99974 - Page: https://openairdocs.org/ntsb/GAA19CA471 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-235, 5 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102810), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-235, 2 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=7102810), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-28-235, 28 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7102810), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: wall/barricade](https://openairdocs.org/ntsb-findings/03022027): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Piper PA-28-235, 1 case](https://openairdocs.org/ntsb-findings/03022027/cases.md?model=7102810), [All aircraft, 29 cases](https://openairdocs.org/ntsb-findings/03022027/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-28-235, 16 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7102810), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) (defining event); cases with it: [Piper PA-28-235, 3 cases](https://openairdocs.org/ntsb-events/370/sequence.md?model=7102810), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-28-235, 35 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102810), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative The pilot reported that the main runway was closed at the high-altitude destination airport, so he planned to make a short-field landing on a perpendicular 2,084 ft runway. 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. The airport's automated weather observation station reported that, about 5 minutes after the accident, the wind was from 150° at 6 knots. The pilot landed the airplane on runway 08. Archived Notices to Airmen (NOTAMs) for the date of the accident stated that: 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 they issued a NOTAM with the intention that pilots could take off on runway 8 and land on runway 26 to avoid construction equipment. He added that airport management had no issues if pilots landed on runway 8, as long as the landing facilitated a headwind and construction equipment was avoided. He reported that the NOTAM for runway 26 meant "closed except full stop landing." ## Aircraft - Registration: [N8641W](https://openairdocs.org/deregistered/N8641W-2022-05-09), registration cancelled 2022-05-09, S/N 28-10158, built 1963 (OpenAirDocs) - Reported make and model: PIPER PA28 (235) - Registry model: [Piper PA-28-235](https://openairdocs.org/model/piper-pa-28-235) (registry code 7102810) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-10158 - Year built: 1963 - Airframe hours: 4413 - Engines: Lycoming O-540 235 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 8, 2019 - Departed: COS, Colorado Spring, CO - Destination: FLY, Falcon, CO - Airport: FLY, Meadow Lake, runway 08, 2,084 × 35 ft, gravel - Equipment: Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 41; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land, single-engine sea; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review March 22, 2018; seat: right; restraint: lap only; flight hours: 1,325.6 total, 221.1 in this make and model, 826.9 as pilot in command, 19.8 in the last 90 days, 1.1 in the last 30 days, 0.1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 150° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: 11,000 ft overcast - Temperature: 66 °F, dew point 54 °F - Observed at: KFLY ## Other investigations on N8641W (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB SEA70FDA09](https://openairdocs.org/ntsb/SEA70FDA09), Jun 1, 1970: Piper PA-28 (N8641W), Baker, MT, substantial damage ## Docket (5 files) The files NTSB released with the investigation on October 18, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=99974. 2.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 620 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476823&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - NTSB 6120.1 Flight Time Amendment (item 2, .PDF, 106 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476824&FileExtension=.PDF&FileName=NTSB%206120.1%20Flight%20Time%20Amendment-Master.PDF - Record of Conversation - Airport Manager (item 3, .PDF, 68 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476825&FileExtension=.PDF&FileName=Record%20of%20Conversation%20-%20Airport%20Manager-Master.PDF - Archived NOTAMs (item 4, .PDF, 24 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476827&FileExtension=.PDF&FileName=Archived%20NOTAMs-Master.PDF - Accident Photos (item 5, .PDF, 2 photos, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40476828&FileExtension=.PDF&FileName=Accident%20Photos-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.