FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA267 · De Havilland DHC6 300

15 Aug 2019 · San Marcos, TX, United States

Berry Aviation De Havilland DHC6 300 · Accident: loss of control in flight on approach

From Gillespie County Airport (T82) to San Marcos Regional Airport (HYI)

Report a problem

Event

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

De Havilland DHC6 300

Aircraft type
de Havilland DHC6
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
N322AV
Onboard fatalities
Unknown
Route
From Gillespie County Airport (T82), Fredericksburg, TXTo San Marcos Regional Airport (HYI), San Marcos, TX
Aircraft age
About 48 years (built 1971)
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 · VFR go-around
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
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The airline transport pilot receiving company flight training was flying an approach; the airplane was too high and entered an increasing descent rate. The flight instructor told the pilot to go around, about the same time the pilot elected to go around. However, the pilot’s corrective control and power inputs did not arrest the descent rate, and the airplane impacted the ground, resulting in substantial damage to the left wing and fuselage. The operator reported there were no mechanical anomalies that would have precluded normal airplane operation.

Probable cause

The pilot's delayed go-around attempt and the flight instructor's delayed remedial action that resulted in a nose-down impact with terrain during an attempted go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA267
Event ID
20190815X44418
Case number
CEN19LA267
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, cause areas. 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: caa38dc1823d7ef55c6ab73794005b4cfd0eedb2fc29014ed6648b60e2cab022; retrieved 2026-09-16T09:45:51.548Z.