FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC05FA021 · Cessna 310R

24 Nov 2004 · Paeonian Spring, VA, United States

Cessna 310R · Accident: in flight collision with terrain/water on approach

From Wilmington International Airport (ILM) to Leesburg Executive Airport (JYO)

Report a problem

Event

NTSB case
NYC05FA021
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
2 · 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
Instrument Meteorological Cond

Cessna 310R

Aircraft type
Cessna 310
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
N310DM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Wilmington International Airport (ILM), Willmington, NCTo Leesburg Executive Airport (JYO), Leesburg, 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
Approach · IFR initial approach
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
In flight collision with terrain/water
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

  • Pilot in command › IFR procedure, not followed
  • Weather condition › Low ceiling

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Arriving in the area of the destination airport, the weather was reported as, 10 statute miles of visibility; overcast clouds at 300 feet; and a temperature and dew point of 56 degrees Fahrenheit. The pilot requested and was subsequently cleared for the localizer approach. About 11 miles from the runway, the pilot failed to intercept the final approach course, and air traffic control provided additional radar vectors to assist him in doing so. About 6 miles prior to the runway threshold, the airplane intercepted the final approach course and began a descent. Twenty seconds later, the airplane made a right turn and began tracking parallel, about 1/2-mile west, of the final approach course. The descent continued to 600 feet, about 5 miles prior to the runway threshold, where the pilot executed a missed approach, and requested to "...go and try another one." On the second approach, about 6 miles prior to the runway threshold, the pilot intercepted the final approach course and began a descent. The airplane continued to track the final approach course, and about 7 miles prior to the runway threshold, the airplane's last radar return was recorded at 700 feet. The airplane came to rest on residential property about 6.5 miles from the runway threshold. A post crash fire consumed the main wreckage. The elevation of at the accident site was 717 feet. Review of the published instrument approach procedure revealed that the final approach fix (FAF) was located 5 miles from the runway threshold. The minimum crossing altitude at the FAF was 1,800 feet. The minimums for the approach were 1 statute mile of visibility, and a minimum descent altitude of 720 feet.

Probable cause

The pilot's failure to follow the published instrument approach procedure, which resulted in an in-flight collision with terrain. A factor related to the accident was the low cloud ceiling.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC05FA021
Event ID
20041210X01968
Case number
NYC05FA021
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: investigation status, coordinates. 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: 82db0a7728690f05a492069ca3156b9b87fc7a66ace3d211312cf497da5d7be9; retrieved 2026-09-20T18:11:40.864Z.