eFlight
Accidents · NTSB ERA13CA142 · Final report

Amateur-built VANS RV-10 accident near Lake Placid, New York, February 21, 2013

On February 21, 2013 at about 11:08 pm local time, a amateur-built VANS RV-10, registered N10FD, was substantially damaged in an accident during maneuvering near Lake Placid, New York (Lake Placid Airport). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

The pilot's improper in-flight planning and decision making, which resulted in attempted visual flight in night instrument meteorological conditions and subsequent impact with terrain.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 21, 2013 · about 11:08 pm local time · cases in 2013
Place
Lake Placid, New York · Lake Placid Airport · cases near this airport · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Amateur-built VANS RV-10
Registration
N10FD · no longer on the register · serial 40090
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot received weather information and filed an instrument flight rules (IFR) flight plan before departure. As the pilot approached his destination, which was surrounded by high terrain, the scattered cloud layer below him became broken and light conditions were dimming as the sun set. After seeing a break in the clouds and being uncomfortable with what he observed, the pilot requested the GPS-A approach then maneuvered to intercept the inbound course at the initial approach fix (IAF). Before reaching the IAF, he saw a clear visual path to his destination. At the same time, the air traffic controller was awaiting cancellation from a landing aircraft and advised that the pilot should expect an instruction to hold. The pilot advised that visual meteorological conditions existed and that he would continue visually. He then turned, descended, and crossed the final approach course inside of the final approach fix. The controller then received the cancellation he had been waiting for and cleared the pilot for the GPS-A approach. The pilot acknowledged and continued his descent. The controller then asked the pilot to cancel his IFR clearance with him or on the ground. The pilot replied with his intention to fly a visual flight rules (VFR) approach and canceled the IFR clearance. The pilot had the town in sight and estimated there was a 2,000-foot ceiling. Light conditions were significantly darker below the cloud layer. He switched to the Unicom frequency and keyed the microphone five times to activate the runway lights but did not see them. He tried twice more, and the lights still did not activate. As the pilot considered whether to climb or circle the airport and try the lights again, he maintained his last heading, which he believed would keep him over lower terrain. However, the airplane drifted right of course. The pilot had decided to climb when a passenger then observed trees. The pilot pulled up to avoid them, but the airplane struck trees and terrain, sustaining substantial damage to the fuselage, wings, and empennage. Radar data revealed that the pilot had never become established on the approach, at no point was in position to land, and was never closer than 1 mile northeast of the airport before flying into rising terrain. No anomalies with airport lighting were discovered. Examination of the GPS-A approach procedure revealed that it was not authorized for use at night. Weather data recorded near the time of the accident indicate visibility below VFR minimums at 2.5 miles in light snow and mist and a 1,400-foot overcast ceiling, which was also below the published minimum descent altitude.

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

  1. VFR encounter with IMC during maneuvering
  2. Controlled flight into terrain or object (CFIT) during maneuvering defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › (general) › Response/compensation
  • cause Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,941 hours in all; 274 in this make and model; 21 in the last 90 days; 9 in the last 30 days
  • Last flight review: May 1, 2012
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 208 hours
  • Last inspection: condition inspection, November 6, 2012
  • Maximum gross weight: 2,700 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming IO-540-D4A5 (piston); 0 hours total

The flight

  • Departed from: SMQ Somerville NJ at 9:03 pm
  • Destination: LKP Lake Placid NY
  • Flight plan: not recorded
  • Runway 32, 4,195 ft by 60 ft

Weather at the time

  • Light: night
  • Visibility: 2 statute miles
  • Sky: overcast at 1,400 ft
  • Temperature: 54°F (12°C), dew point 57°F (14°C)
  • Altimeter: 30.12 inHg
  • Observation at 11:07 pm from SLK, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

9 documents, released by the NTSB on June 4, 2013. 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.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA13CA142.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.