FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA17LA042 · North American NAVION UNDESIGNAT

10 Nov 2016 · Blairstown, NJ, United States

North American NAVION UNDESIGNAT · Accident: loss of control on ground while standing

From Blairstown Airport (1N7) to Capital City Airport (CXY)

Report a problem

Event

NTSB case
ERA17LA042
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
1 · 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 NAVION UNDESIGNAT

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
N8849H
Operator
Unknown
Onboard fatalities
Unknown
Route
From Blairstown Airport (1N7), Blairstown, NJTo Capital City Airport (CXY), Harrisburg, PA
Aircraft age
About 69 years (built 1947)
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
Standing · engine(s) start-up
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
Loss of control on ground
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
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

**This report was modified on April 10, 2025. Please see the docket for the original report.** The private pilot had not flown the accident airplane for almost 1 year while it underwent repairs following a gear-up landing. The purpose of the accident flight was to ferry the airplane to a nearby airport to receive an annual inspection after completion of the repairs. On the morning of the accident, a mechanic taxied the airplane and performed an engine run-up; he did not note any anomalies. The pilot fueled the airplane and started the engine for the flight. Upon starting, the engine went immediately to full power, where it remained as the airplane taxied at high speed about 1,000 ft into a tree. Witnesses reported that the pilot was awake and alert after the accident; thus, there was no evidence of pilot incapacitation. Examination of the wreckage did not reveal any preimpact mechanical malfunctions or anomalies. The preaccident position and functionality of the throttle and mixture controls could not be determined due to damage sustained during the event; however, it is likely that the throttle control was pulled forward during the accident sequence. Further, the mechanic conducted an unremarkable taxi and run-up before the accident, and the engine immediately climbed to full power after the pilot started it. Considering the pilot’s subsequent failure to avail himself of multiple other avenues to halt or slow the airplane, including applying the brakes, cutting the engine mixture, or turning off the magnetos, the pilot likely performed a hot start procedure to purge the lines of the hot fuel and vapor from the run-up and taxi, failed to reduce the throttle afterward and, possibly startled by the sudden onset of engine power, was unable to regain control of the airplane.

Probable cause

The pilot's improper engine start procedure, which resulted in a loss of control on the ground and collision with a tree.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA17LA042
Event ID
20161111X91241
Case number
ERA17LA042
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: e78397a609344b2a8d62bb41071b67cb0dce5cf145cb35ffb4b19f57ee7f3041; retrieved 2026-09-14T22:02:11.984Z.