FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA13CA008 · Bombardier Inc DHC-8-315

17 Oct 2012 · Kabul, Afghanistan

US Department Of State Bombardier Inc DHC-8-315 · Accident: hard landing

From Tarinkot Airport (OATN) to Kabul International Airport (OAKB)

Report a problem

Event

NTSB case
DCA13CA008
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
Government
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

Bombardier Inc DHC-8-315

Aircraft type
Bombardier DHC-8
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
N800AW
Onboard fatalities
Unknown
Route
From Tarinkot Airport (OATN), TarinTo Kabul International Airport (OAKB), Kabul
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
Public Aircraft
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
Landing · flare/touchdown
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
Hard landing
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 › Task performance

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

NTSB narrative

On October 17, 2012, about 1119 local time, 0649 Coordinated Universal Time (UTC), a Bombardier DHC-8-315, registration N800AW, operated by the United States Department of State, experienced a hard landing on runway 29 at Kabul International Airport (OAKB) Kabul, Afghanistan. There were no injuries to the three passengers or three crewmembers onboard and the aircraft was substantially damaged. Visual meteorological conditions prevailed at the time. The flight had originated from Tarin Kowt Airport (OATN), Tarin Kowt, Afghanistan

According to the flight crew, the takeoff, climb and cruise were uneventful. The captain was the flying pilot. At 11:12 the flight was cleared for the approach and at 11:16 the flight crew selected flaps 35 and initiated a random steep approach in accordance with company task procedures as a result of the airport threat level. According to the flight crew statements, the airplane engine power was reduced to idle for the approach and was not increased prior to landing. Information obtained from Flight Data Recorder (FDR) indicated engine torque was at or near zero for the last 5 minutes of approach and landing.

The aviation routine weather report at 0550 local time indicated wind from 120 degrees at 5 knots, 8000 meters visibility and temperature 17 degrees C. For the two minutes prior to landing, the wind was light and variable. A tactical meteorological observation system on the field reported the wind direction during the two minutes prior to landing as variable from 004 degrees to 137 degrees and the wind speed variable from 1 knot to 7.2 knots. Wind gust recorded during the time period varied from 050 degrees to 079 degrees at 7.0 to 7.2 knots.

Based on FDR data the calculated rate of descent was about 2,000 feet per minute during approach, reducing to about 1,500 feet per minute just prior to landing. The airplane touched down with a nose up pitch attitude of approximately 8 degrees and a peak vertical acceleration of 2.7g. The airplane geometry information provided by the manufacturer indicated that aft fuselage contact will result from a pitch attitude over 11.9 degrees with an extended landing gear oleo strut, and a pitch attitude over 6.8 degrees with a compressed landing gear oleo strut.

In order to avoid nuisance warnings resulting from the random steep approach (i.e. steep angle descent), the flight crew deactivated the ground proximity warning system (GPWS) for approach. As these alerts would be expected by the crew during this type of approach, it is unlikely the alerts would have prompted the crew to take corrective action.

The airplane touched down and contacted the aft fuselage on the runway resulting in substantial damage (including buckled, cracked, and bent frames and stringers).

Probable cause

the captains ineffective management of the airplanes energy state during final approach and flare that resulted in a hard landing and tail strike at touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA13CA008
Event ID
20121025X02835
Case number
DCA13CA008
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: 4c83dcdb1a3ff80a1bf9937f19da0a87bf49f2be4423ddc8ebf7183559b63675; retrieved 2026-09-15T20:16:54.287Z.