Amateur-built VANS RV-10 accident near Limon, Colorado, December 8, 2017
On December 8, 2017 at about 2:50 am local time, a 2010 amateur-built VANS RV-10, registered N9738J, was substantially damaged in an accident during approach near Limon, Colorado (Limon Muni airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- December 8, 2017 · about 2:50 am local time
- Place
- Limon, Colorado · Limon Muni · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built VANS RV-10 NO SERIES, built 2010
- Registration
- N9738J · no longer on the register · serial 40296
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Other weather encounter during approach
- Collision during takeoff/land during approach defining event
- Hard landing during landing
- Collision with terrain or object (not controlled flight into terrain) during landing
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
- cause Environmental issues › Physical environment › Object/animal/substance › Wire › Effect on operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation
- Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on personnel
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 355 hours in all; 259.3 in this make and model; 109.9 in the last 90 days; 28.3 in the last 30 days; 315 as pilot in command
- Last flight review: March 23, 2017
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 925 hours
- Last inspection: 100-hour inspection, October 5, 2017
- Maximum gross weight: 2,700 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming IO-540-X (piston); 980 hours total
The flight
- Departed from: OJC Olathe KS at 11:45 pm
- Destination: LIC Limon CO
- Flight plan: none
- Runway 34, 4,700 ft by 60 ft
Weather at the time
- Light: night, dark
- Wind: from 330° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 27°F (-3°C), dew point 10°F (-12°C)
- Altimeter: 30.13 inHg
- Observation at 2:55 am from KLIC
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on January 25, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Accident Photo | PDF, 1 page | View Download |
| 3 | FAA Roc | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.