FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC07FA217 · Piper PA-28-140

6 Sept 2007 · Syria, VA, United States

Piper PA-28-140 · Accident en route

From Hartsville Regional Airport (HVS) to Winchester Regional Airport (OKV)

Report a problem

Event

NTSB case
NYC07FA217
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
3 · 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

Piper PA-28-140

Aircraft type
Piper PA-28
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
N6493W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartsville Regional Airport (HVS), Hartsville, SCTo Winchester Regional Airport (OKV), Winchester, VA
Aircraft age
Not recorded
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
En route · cruise
First occurrenceThe 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
Miscellaneous/other
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

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

NTSB narrative

The accident airplane was on a direct course to its destination airport during dark night with mountainous terrain off its left side. The pilot had accumulated approximately 140 total hours of flight experience and was not instrument-rated. While descending to 3,500 feet above mean sea level (msl), the airplane turned off its established course to the east. When queried by the approach controller, the pilot responded he was heading 045 degrees. When asked again to say his heading, he responded he was on a 107-degree heading, but should be on a 025-degree heading, and was making a left turn "towards my course." He then was told to proceed on course and advised to maintain "Ground avoidance, obstacle avoidance as you are in a 5,600 foot minimum vectoring altitude area." No further transmissions were received and moments later radar contact lost by the approach control facility. Review of radar data also revealed that the accident airplane’s ground speed and ground track had begun to fluctuate just prior to the controller’s query and that after the airplane turned back to the left, altitude decreased, airspeed increased, and radar contact was then lost. The wreckage was discovered on the side of a mountain at 2,848 feet msl. No evidence of any preimpact malfunction of the airplane or engine was discovered. A report from another pilot to the approach controller revealed that there was no visible horizon or visible ground lighting in the area where the accident airplane went off radar. The FAA's Pilot's Handbook of Aeronautical Knowledge (FAA-H-8083-25) stated, "Unless a pilot has many hours of training in instrument flight, flight in reduced visibility or at night when the horizon is not visible should be avoided."

Probable cause

The pilot's inadvertent flight into instrument meteorological conditions and his failure to maintain aircraft control. Contributing to the accident was the dark night conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC07FA217
Event ID
20070917X01406
Case number
NYC07FA217
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2007-09-07.
  • API snapshot SHA-256: 961d4873a1a47f32ef1fb8affd46dd49b1bb84df695cc6ae2ea5c9b7d29d681e; retrieved 2026-09-20T16:18:26.529Z.