FlarePathAir-accident investigation intelligence
Investigation brief · generated 2026-10-09 · source: NTSB public docket and accident database

AIRBUS INDUSTRIE A320 211 — Rapid City, SD, USA, 2016-07-08

NTSB number
DCA16IA200
Operator
DELTA AIR LINES INC
Registration
N333NW
Highest injury
No injury
Regulation
Part 121
Damage
—
Cohort
Part 121 airline
Recorder data
Tier 1 — decoded recorder tables
Every sentence below is taken directly from NTSB records — the accident database, the docket's recorder reports and the Board's findings — with its source noted. Nothing is paraphrased or inferred.

NTSB summary

The flight was routine until nearing the Rapid City terminal area.  The crew had initially briefed for landing on runway 32, but the wind had shifted and favored runway 14.  The crew reported that they had prepared for the runway 14 approach as well, so the change was not a significant factor.  Delta chart material did include an advisory regarding the close proximity and alignment of the two airports. Landing on runway 14 required more flying distance than runway 32, however, at 2030, the crew discussed the need to descend more rapidly.  The flight was not altitude restricted by ATC.  At 2035, ATC instructed the flight to fly heading of 300 degrees for the downwind leg of the visual approach.  At that time the airplane was 9 miles abeam RAP at 12,000 feet.  The ATC controllers noted that the airplane was high and fast for the visual approach.  Field elevation of RAP was 3,200 feet and with a nominal remaining flying distance of about 15 to 18 miles the airplane was positioned well above the typical 300 feet per mile descent.  At 2036:30 the captain called the airport in sight and called for gear down and flaps one, configuring the airplane for a more expeditious descent.  At this point RAP was south-southwest of the airplane, at the 8 o'clock position, while RCA was at the 10 o'clock position, therefore, it is likely the captain was actually looking at RCA. Shortly afterward, ATC issued a vector for base leg, but the crew requested to extend the downwind due to high altitude, which ATC approved.  At 2039, the crew accepted a turn to base leg as the airplane was descending through 5,800 feet, about 5.5 miles north of RCA, and about 12 miles north of RAP.  This was consistent with altitudes on the RNAV14 approach to RAP, but a somewhat steeper than normal angle to RCA.  ATC cleared the flight for "visual approach runway one-four. Use caution for Ellsworth Air Force Base located six miles northwest of Rapid City Regional."  FAA order 7110.65 directs controllers to describe the location of a potentially confusing airport in terms of direction/distance from the aircraft.  During interviews, the crew stated they misheard the controller's warning for the typical position advisory given on an instrument approach, and it supported their idea that the correct landing runway was 6 miles away.  The FO did query the Captain if he had the right airport in sight, who expressed some uncertainty.  Both crewmembers had little to no experience flying into either RAP or RCA, however, they did not verify their position to the desired landing runway using either the automation, or by querying ATC; and switched off the autopilot and Flight Directors removing possible cues as to their position related to RAP  At the time ATC cleared the flight for the visual approach  the airplane was positioned on the final approach course of the RNAV14 approach, and at a reasonable altitude for that approach, therefore, there was no immediate indication to ATC that the crew had identified the wrong airport. Shortly after, the captain increased the descent rate as high as 1,200 feet per minute, resulting in an unstable approach as he was focused on the wrong landing runway.  The crew realized the mistake just prior to touchdown, but considered it was safer to complete the landing at that point.
Verbatim, NTSB aviation accident database (narratives.narr_accf).

Probable cause

The flight crew's misidentification of the desired landing runway due to excess altitude requiring an extended downwind, and failure to use all available navigation information.
Verbatim, NTSB determination.

Flight data recorder

Airbus A320, FDR · N333NW — 247,392 samples, 50 parameters, 19:20:00.0 to 23:27:30.0.

ParameterMaxatMinatFinalat
Pressure altitude ft36,048.020:03:17.936.019:32:41.93,112.023:27:29.9
Pitch attitude deg17.619:26:34.2-4.620:28:34.40.023:27:29.9
Roll attitude deg25.019:27:11.9-28.820:39:35.90.023:27:29.9
Vertical acceleration g1.323:26:33.00.823:26:33.51.023:27:29.9
Magnetic heading deg324.523:26:35.139.020:43:59.1323.823:27:29.1
Computed from the docket's tabular attachment; times as recorded (local or SRN as published).

Sequence of events (FDR factual report)

TimeEventPage
19:25 MDTThe aircraft departed MSP at about 19:25 MDT and a climbed to a final cruising altitude of flight level 3603
20:25:28 MDTThe aircraft began a descent when it was about 76 nautical miles (nm) from RAP3
20:35:52 to 20:36:50 MDTThe aircraft leveled at 10,000 ft as its speed slowed below 250 knots indicated airspeed (KIAS)3
20:36:31 MDTSpoilers were applied during the level-off at 10,000 ft, used until about 20:38:58 MDT (with a retraction for about 15 seconds during this time)3
20:36:50 MDTThe aircraft was abeam RCA and about 8.5 nm from RAP and 5.5 nm from RCA3
20:37:03 MDTThe gear was selected down, when the aircraft was descending through 9,770 ft and was 5.5 nm abeam from RCA3
20:37:12 MDTFlaps 1 were selected3
20:37:58 MDTFlaps 2 were selected, when the aircraft was about 4.8 nm northeast of RCA and 10 nm northeast of RAP3
20:38:14 MDTFlaps 3 were selected3
20:39:46 MDTFlaps 4 were selected, as the aircraft was in a left turn towards the RAP RNAV 14 final approach course4
20:40:44 MDTThe autopilot was turned off, as the aircraft was nearly on the RAP RNAV 14 final approach course4
20:41:05 MDTThe flight directors were turned off, as the aircraft deviated left of the RAP RNAV 14 final approach course, was aligned with the runway 13 extended centerline at RCA, and was about 2.8 nm from the approach end of RCA runway 134
20:42:42 MDTThe aircraft landed at RCA4
Extracted by claude-sonnet-5; 12 of 13 stated events verified against the raw recorder data.

Cockpit voice recorder

1369 transcribed utterances from 19:26:49.8 to 23:37:20.6, 21 sources. Final entries:

23:34:59.5HOT[sound of beep]
23:35:06.5CAM[sound of unintelligible chatter from cabin]
23:37:09.1CAM[sound of chime]
23:37:14.8CAM[sound of discontinuity in recording, similar to CVR power cycle]
23:37:20.6CAM[sound of unintelligible voices]
The NTSB cautions that a CVR transcript is not a precise science and should not be used as the sole source of information.

Recorder documents in the docket

GroupTitlePagesType
fdrFLIGHT DATA RECORDER - SPECIALIST'S FACTUAL REPORT22pdf
fdrFLIGHT DATA RECORDER - ATTACHMENT 1 - TABULAR DATA (COMPRESSED ZIP ARCHIVE)zip
cvrCOCKPIT VOICE RECORDER - GROUP CHAIRMAN'S FACTUAL REPORT153pdf

Docket: data.ntsb.gov/Docket/?NTSBNumber=DCA16IA200. This brief is an analytical aid assembled from public records; it is not an investigative finding.