ERA13CA389 · Diamond Aircraft IND Inc DA 40
GLM Advisory Diamond Aircraft IND Inc DA 40 · Accident: VFR encounter with IMC en route
From Charleston Executive Airport (JZI) to Western Carolina Regional Airport (RHP)
Event
- NTSB case
- ERA13CA389
- 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
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
- N447JP
- Operator
- GLM Advisory
- Onboard fatalities
- Unknown
- Route
- From Charleston Executive Airport (JZI), Charleston, SCTo Western Carolina Regional Airport (RHP), Andrews, NC
- Aircraft age
- About 9 years (built 2004)
- 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 · descent
- 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
- VFR encounter with IMC
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was at 6,500 feet mean sea level (msl) when he encountered a dark cloud. The pilot decided to descend to 4,500 msl through a “hole” in the clouds and when he “popped” out of the cloud he realized he was going to impact trees. He pulled back on the yoke and the airplane subsequently impacted trees and terrain. A postaccident examination of the airplane by a Federal Aviation Administration inspector revealed the left wing and empennage had separated from the airplane post-impact. The pilot reported no pre-impact mechanical malfunctions or failures that would preclude normal operations.
Probable cause
The pilot’s decision to continue visual flight into deteriorating weather, which resulted in an encounter with instrument meteorological conditions and subsequent inability to maintain clearance with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA389
- Event ID
- 20130830X72351
- Case number
- ERA13CA389
- 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: 9df623f58ae68fe126df41ac0d998679b73511b6b09cdc26fc22c465a86e0498; retrieved 2026-09-15T22:40:54.189Z.