FlarePath
Cases › DCA16IA036 › The analyst

BOEING 737ALASKA AIRLINES INC

What the docket says, assembled. No language model is involved, so nothing on this page can be invented — every line traces to a recorder, a report page or the Board's own record.

0
timed facts
8
precedents
10
passages to ask

Ask the docket

passages, not paraphrases
Try

Every answer is a passage of the docket with the page it came from, or the words “not in the docket”. Nothing is summarised or reasoned for you — read the source.

One timeline

0 timed factsthe recorder events from the FDR report, with the transcript's warnings, callouts, the words nearest each event and the final seconds — on one clock, as printed in each report

No timed facts: this docket has no extracted recorder sequence and no transcript.

Recorder events without a clock time
  • 0824:50 PSTThe aircraft turned towards the airport
  • 0829:09 PSTThe aircraft made a slight course change and lined up with taxiway "T" at SEA
  • 0831 PSTThe airplane landed on taxiway "T" instead of the intended runway 16C
FLIGHT DATA RECORDER - SPECIALIST'S FACTUAL REPORT · 3 events extracted by claude-sonnet-5
How the Board coded the sequence
  1. Landing-flare/touchdown: Wrong surface or wrong airport

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • DCA25LA1632025-03-20no fatalitiesmatch 79
    BOEING 737-8H4 · SOUTHWEST AIRLINES CO
    Orlando, FL
    • ●Personnel issues › Action/decision › Info processing/decision
    Wrong surface or wrong airport
  • OPS11IA2732010-12-31no fatalitiesmatch 73
    EMBRAER ERJ190 · Air Canada
    Denver, CO
    • ●Personnel issues › Action/decision › Info processing/decision
  • DCA18IA0812017-12-30no fatalitiesmatch 73
    BOMBARDIER INC DHC 8 402 · HORIZON AIR INDUSTRIES INC
    Pullman, WA
    • ●Personnel issues › Action/decision › Info processing/decision
    Wrong surface or wrong airport
  • OPS17IA0082016-12-15no fatalitiesmatch 73
    BOMBARDIER INC CL 600 2B19 · SKYWEST AIRLINES INC
    San Francisco, CA
    • ●Personnel issues › Action/decision › Info processing/decision
  • DCA15FA0042014-10-05substantialmatch 70
    EMBRAER EMB 145LR · CHAUTAUQUA AIRLINES INC
    Jamaica, NY
    • ●Personnel issues › Action/decision › Info processing/decision
  • ANC13FA0302013-03-082 fatalmatch 65
    BEECH 1900C · ALASKA CENTRAL EXPRESS INC
    Aleknagik, AK
    • ●Personnel issues › Action/decision › Info processing/decision
  • DCA22LA1262022-06-08no fatalitiesmatch 63
    BOEING 757-236 · Federal Express Corporation
    Tulsa, OK
    • ●Personnel issues › Action/decision › Info processing/decision
    Wrong surface or wrong airport
  • DCA11FA0502011-01-03substantialmatch 62
    BOEING 737-823 · American Airlines
    Los Angeles, CA
    • ●Personnel issues › Action/decision › Info processing/decision

What the record says

a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause
Findings the Board cited in those cases
Occurrences it coded
  • 3 of 8Wrong surface or wrong airport
  • 2 of 8Runway incursion veh/AC/person
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Action/decision › Info processing/decision
Cited here, not seen in the precedents
  • —
Common in the precedents, not cited here
  • Action/decision › Action

A teaching device, not a verdict: what the record would have looked at, next to what the Board found.

In the Board’s words — the closest cases
  • DCA25LA1632025-03-20 · BOEING 737-8H4 · SOUTHWEST AIRLINES CO
    The captain’s failure to recognize that the airplane’s location did not agree with the assigned departure runway as required per the Southwest Airlines Airplane Operating Manual, and the captain’s plan continuation error when he missed several cues that would have informed him that he was not on the assigned departure runway when he initiated takeoff.
  • OPS11IA2732010-12-31 · EMBRAER ERJ190 · Air Canada
    The driver of the operation vehicle's misidentification of the runway for an adjacent taxiway, resulting in a runway incursion with an aircraft in position for takeoff.
  • DCA18IA0812017-12-30 · BOMBARDIER INC DHC 8 402 · HORIZON AIR INDUSTRIES INC
    the flight crew's misidentification of the taxiway as the landing runway due to the failure of the runway lighting that caused only the taxiway lights to be illuminated.
  • OPS17IA0082016-12-15 · BOMBARDIER INC CL 600 2B19 · SKYWEST AIRLINES INC
    The captain’s inadvertent turn onto the incorrect taxiway and subsequent entry onto an active runway without a clearance, which resulted in the runway incursion.
  • DCA15FA0042014-10-05 · EMBRAER EMB 145LR · CHAUTAUQUA AIRLINES INC
    The A340 captain's failure to maintain adequate clearance between his wing and the tail of the EMB-145.

This is the pattern in the NTSB’s own record across similar accidents — which findings it cited, what it coded, what it recommended. It is drawn from the record, not written about this case, and it never assigns blame: investigations exist to prevent the next accident (ICAO Annex 13).