FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA238 · North American AT6 - C

9 May 2014 · Roxbury, NY, United States

North American AT6 - C · Accident: landing area overshoot

From Lake County Executive Airport (LNN) to Roxbury Runway Airport (1NK0)

Report a problem

Event

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

North American AT6 - C

Aircraft type
North American AT6
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
N164EW
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake County Executive Airport (LNN), Willoughby, OHTo Roxbury Runway Airport (1NK0), Roxbury, NY
Aircraft age
About 71 years (built 1943)
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 · flare/touchdown
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 overshoot
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire
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 › Psychological

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

NTSB narrative

According to pilot he checked the weather at his destination airport and it called for VFR weather. While enroute to his destination he stated that the weather was deteriorating and the ceilings were getting low. As a precaution he started to look for a place to land since the weather was closing in and his fuel was also getting low. The pilot located a private grass strip and made an attempt to land. As the airplane touched down on the field the pilot applied the brakes, but he had little brake response due to the wet grass. When the pilot relized that he would be unable to stop the airplane prior to the end of the runway, he initiated a go-around and struck a power line follow by trees before losing control and colliding with the ground. The airplane sustained substantial damage to both wings and the fuselage. The pilot did not report any mechanical anomalies that would have precluded normal operation prior to the accident.

Probable cause

The pilot's failure to maintain adequate obstacle clearance, which resulted in the inflight collision with a power line.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA238
Event ID
20140513X62510
Case number
ERA14CA238
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • 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 local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: a50de55b998da80bd9a55d06dfccfdb80bd769c29dbbfe15073899db61689c30; retrieved 2026-09-15T23:37:25.657Z.