FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA083 · Diamond Aircraft IND Inc DA 40

10 Dec 2012 · Lake Park, GA, United States

Diamond Aircraft IND Inc DA 40 · Accident: loss of control in flight en route

From Valdosta Regional Airport (VLD) to Jesup Wayne County Airport (JES)

Report a problem

Event

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

Diamond Aircraft IND Inc DA 40

Aircraft type
Diamond DA-40
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
N840DS
Operator
Unknown
Onboard fatalities
Unknown
Route
From Valdosta Regional Airport (VLD), Valdosta, GATo Jesup Wayne County Airport (JES), Jesup, GA
Aircraft age
About 5 years (built 2007)
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 · climb to cruise
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 in flight
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 › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

Before departing at night for his destination airport, the noninstrument-rated pilot received a weather briefing, which advised of marginal visual flight rules (MVFR) conditions. The briefing also included an airmen's meteorological information advisory for developing instrument flight rules conditions due to low ceilings and mist. Shortly after takeoff, the pilot contacted a radar approach controller for visual flight rules flight-following services, and he was advised to squawk a beacon code, but, before the approach controller was able to identify the airplane on the radar, the pilot radioed, "I'm in trouble." Shortly after, both radar and radio contact were lost. Review of radar data indicated that the airplane's climb rate was steady until the airplane reached an altitude of about 2,100 ft msl. The airplane then began descending rapidly while turning right until it impacted terrain.

Examination of the wreckage did not reveal any evidence of preimpact failures or malfunctions of the engine or primary flight controls. However, examination of the elevator trim system revealed that the elevator trim cable was disconnected from the trim control wheel in the cockpit and that it had pulled out of a swaged rod end (bolt), which displayed a longitudinal crack on the outer surface of the swage. Examination of the fracture surface revealed that the fracture occurred due to overstress. The examinations were not able to determine if the cable pulled out of the fitting during the accident sequence or if it was a pre-existing condition. Regardless, review of the elevator pitch control system revealed that, even if the elevator trim cable had disconnected in flight, it should not have led to an uncontrollable situation due to its redundant design.

At the time of the accident, both the sun and the moon were more than 15 degrees below the horizon. Further, warm, moist southerly wind ahead of an approaching cold front was producing variable clouds, and a band of low stratiform clouds with their tops near 4,000 ft existed over the area. Operating in MVFR conditions increases a pilot's workload and stress level because navigation becomes more difficult and reduces the margin of safety. As a result of the increased workload and stress level and the pilot's minimal simulated instrument time (about 7 hours); his minimal night experience (about 3 hours); the dark, night MVFR conditions; restricted visibility, including a lack of ambient light; and the sustained right turn and descent, it is likely the pilot experienced spatial disorientation and subsequently lost control of the airplane.

Probable cause

The noninstrument-rated pilot’s improper decision to depart in dark, night marginal visual flight rules conditions, which resulted in his spatial disorientation and subsequent loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA083
Event ID
20121211X41020
Case number
ERA13FA083
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-12-11.
  • API snapshot SHA-256: 164731763130fd2f6d6a563a8b78d9918a6ccd3bb16dfc733cd96266300fcb5c; retrieved 2026-09-14T15:50:30.152Z.