# NTSB GAA18CA075: Jones Kent C Vans RV-10, N9738J, Limon, CO, December 8, 2017 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: December 7, 2017, 19:50 local (Dec 8, 2017, 02:50 UTC) - Place: Limon, CO - Coordinates: 39.275001, -103.665832 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.2750&lon=-103.6658&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report February 21, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 96442 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA075 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96442/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96442 - Page: https://openairdocs.org/ntsb/GAA18CA075 ## Probable cause The pilot’s unstabilized approach and failure to go around at night, which resulted in the airplane impacting a power line and a subsequent hard 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: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=05627XA), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Object/animal/substance: wire](https://openairdocs.org/ntsb-findings/03022032): Environmental issues › Physical environment · Effect on operation (probable cause); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/03022032/cases.md?model=05627XA), [All aircraft, 588 cases](https://openairdocs.org/ntsb-findings/03022032/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05627XA), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=05627XA), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Wind: gusts](https://openairdocs.org/ntsb-findings/03034045): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/03034045/cases.md?model=05627XA), [All aircraft, 1,199 cases](https://openairdocs.org/ntsb-findings/03034045/cases.md) - [Light condition: dark](https://openairdocs.org/ntsb-findings/03036020): Environmental issues › Conditions/weather/phenomena · Effect on personnel; cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/03036020/cases.md?model=05627XA), [All aircraft, 448 cases](https://openairdocs.org/ntsb-findings/03036020/cases.md) - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=05627XA), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-events/400/sequence.md?model=05627XA), [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Approach: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=05627XA), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing: Hard landing](https://openairdocs.org/ntsb-events/092); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-events/092/sequence.md?model=05627XA), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Jones Kent C VANS RV-10, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05627XA), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, during a night approach, the runway precision approach path indicator lights indicated that the airplane was on a proper glidepath. Shortly after, the airplane encountered a "strong gust of wind" and "lost significant altitude." He added engine power and raised the airplane's nose to intercept the glidepath. A few seconds later, he felt a slight bump and heard a scraping noise to his right. He looked to the right, and when he returned his focus to the approaching runway, he noticed that the airport lights were no longer lit, and the airport was in "complete darkness." He added that he "couldn't really see anything and wasn't sure exactly where the runway was, [but he] knew [he] was going to have a hard landing." He then pulled the power back, moved the mixture to idle cut off, and turned the fuel selector off. Subsequently, the airplane landed hard off the runway, bounced, slid sideways, struck a tree, and then came to rest. The airplane sustained substantial damage to the fuselage, both wings, and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Following the accident, it was discovered that, during the approach, the airplane struck a power line that supplied the airport power. The automated weather observation system at the accident airport reported that, about the time of the accident, the wind was from 330° at 6 knots. The pilot was on a visual approach for runway 34. According to the Federal Aviation Administration inspector assigned to the accident, the power line was estimated to be 75 ft above the ground and 1/2 mile from the runway threshold. The power line crossed perpendicular to the runway. ## Factual narrative The pilot reported that, during a night approach, the runway Precision Approach Path Indicator lights indicated the airplane was on a proper glide path. Shortly afterward, the airplane encountered a "strong gust of wind" and "lost significant altitude". He added engine power and raised the airplane's nose to intercept the glide path. A few seconds later, he felt a slight bump and heard a scraping noise to his right. He looked to the right and when he returned his focus to the approaching runway, he noticed that the airport lights were no longer lit, and the airport was in "complete darkness". He added that, he "couldn't really see anything and wasn't sure exactly where the runway was, [but he] knew [he] was going to have a hard landing". He then pulled the power back, moved the mixture to idle cut off, and turned the fuel selector off. Subsequently, the airplane landed hard off the runway, bounced, and slid sideways coming to rest after striking a tree. The airplane sustained substantial damage to the fuselage, both wings and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Following the accident, it was discovered that during the approach the airplane struck a powerline that supplied the airport power. The automated weather observation system at the accident airport reported, about the time of the accident that the wind was from 330° at 6 knots. The pilot was on a visual approach for runway 34. According to the Federal Aviation Administration investigator assigned to the accident, stated in a telephone conversation with the National Transportation Safety Board investigator in charge, the powerline was estimated to be 75 ft. above the ground and one half mile from the runway threshold. The powerline crossed perpendicular to the runway. ## Aircraft - Registration: [N9738J](https://openairdocs.org/deregistered/N9738J-2020-08-21), registration cancelled 2020-08-21, S/N 40296, built 2010 (OpenAirDocs) - Reported make and model: JONES KENT C VANS RV-10 (NO SERIES) - Registry model: [Jones Kent C VANS RV-10](https://openairdocs.org/model/jones-kent-c-vans-rv-10) (registry code 05627XA) (OpenAirDocs) - Registry engine: [Lycoming IO-540-EXP](https://openairdocs.org/engine/lycoming-io-540-exp) (registry code 42167, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 40296 - Year built: 2010 - Airframe hours: 925 - Engines: Lycoming IO-540-X 290 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: 100 hour, October 5, 2017 - Departed: OJC, OLATHE, KS - Destination: LIC, Limon, CO - Airport: LIC, Limon Muni, runway 34, 4,700 × 60 ft, concrete - Equipment: ADS-B, Stall warning system, Satellite tracking device, Onboard weather, Electronic primary flight display, Electronic multifunction display, Electronic flight bag or handheld device, Auto-pilot, Angle of attack indicator ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 45; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review March 23, 2017; seat: left; restraint: 4-point; flight hours: 355 total, 259.3 in this make and model, 315 as pilot in command, 109.9 in the last 90 days, 28.3 in the last 30 days ## Weather - Conditions: Visual (VMC), Night/dark - Wind: 330° at 6 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 27 °F, dew point 10 °F - Altimeter: 30.13 inHg - Observed at: KLIC ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20171207022829A](https://openairdocs.org/incident/20171207022829A), Dec 7, 2017: Jones Kent C VANS RV-10, Limon, CO, Substantial damage. On the evening of November 07, 2017 at approximately 2000 MST, N9738J came into contact with powerlines while executing a final approach into runway 34 at… ## Docket (3 files) The files NTSB released with the investigation on January 25, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96442. 2.5 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 2.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40459562&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Accident Photo (item 2, .PDF, 312 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40459563&FileExtension=.PDF&FileName=Accident%20Photo-Master.PDF - FAA roc (item 3, .PDF, 171 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40459564&FileExtension=.PDF&FileName=FAA%20ROC-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.