Alaska Airlines Flight 75
Boeing 737-400 · Accident: dragged wing, rotor, pod, float or tail/skid during landing
From Seattle–Tacoma International Airport (SEA) to Juneau International Airport (JNU)
Event
- NTSB case
- ANC98LA122
- 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
- 0
- 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
- Airline
- 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
Boeing 737-400
- Aircraft type
- Boeing 737
- 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
- N799AS
- Operator
- Alaska Airlines
- Onboard fatalities
- Unknown
- Route
- From Seattle–Tacoma International Airport (SEA), Seattle, WATo Juneau International Airport (JNU)
- 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
- Part 121: Air Carrier
- 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
- First occurrenceThe 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
- Dragged wing, rotor, pod, float or tail/skid
- 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
- Flightcrew › Recovery from bounced landing, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain/check airman reported that the accident flight was the first officer's second Initial Operating Experience (IOE) training flight after being hired by the airline. He stated that the first officer was making a visual approach to runway 26, and on initial touchdown the airplane 'skipped' and became airborne. The captain stated that during the initial touchdown he noted that the throttles were not in the fully retarded position. The captain said that at this point, he closed the throttles and instructed the first officer to maintain attitude as the second touchdown approached. He said that the auto spoilers then deployed, and the airplane settled onto the runway in a nose high attitude. The captain characterized the second touchdown as 'firm', but well within acceptable limits. After landing rollout, the airplane was taxied to the gate, and all of the 140 passengers disembarked the airplane uneventfully. A subsequent inspection by ground personnel discovered a 1 foot by 4 feet scrape located on the belly of the airplane, between station 887 and 941.
Probable cause
The flight crew's inadequate recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC98LA122
- Event ID
- 20001211X10743
- Case number
- ANC98LA122
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: d27573e7b65db03b40b8b2308727a8240d4db9483938135d4d34dfc2e9396745; retrieved 2026-09-18T17:05:49.781Z.
- The NTSB's operator name is blank for N799AS; the operator shown is the name the NTSB records it doing business as.