FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

America West Airlines Flight 598

25 Aug 2001 · Kansas City, MO, United States

Boeing 737-3G7 · Accident: loss of control on ground/water during landing

From Phoenix Sky Harbor International Airport (PHX) to Kansas City International Airport (MCI)

Report a problem

Event

NTSB case
CHI01FA292
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
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Boeing 737-3G7

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
N306AW
Onboard fatalities
Unknown
Route
From Phoenix Sky Harbor International Airport (PHX), Phoenix, AZTo Kansas City International Airport (MCI), Kansas City, MO
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
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
Loss of control on ground/water
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

  • Copilot/second pilot › Directional control, not maintained
  • Copilot/second pilot › Proper alignment, not maintained
  • Copilot/second pilot › Proper touchdown point, exceeded
  • Pilot in command › Go-around, not performed
  • Pilot in command › Supervision, inadequate

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

NTSB narrative

The transport airplane sustained substantial damage during landing when it veered off the left side of runway 27 at 0111 cst and both engines sustained foreign object damage (FOD). Level 4 and 5 thunderstorms were in the vicinity of the airport at the time of the accident. The ASOS rain gauge on the airport indicated 0.42 inches of rain fell between 0100 and 0111. The wind was from the northwest at less than 10 knots, and no significant low-level windshear was present at the time of the accident. The first officer was the flying pilot. The Flight Data Recorder data indicated the airplane was on a stabilized instrument approach with the autopilot engaged until about 200 feet above ground level (agl), when the autopilot was disconnected and the airplane was flown manually. After the autopilot disconnect, the airplane began drifting left and above glide slope. The airplane crossed the runway threshold at about 57 feet agl, offset about 65 feet left of centerline, but the ground track was being corrected back toward centerline. A flare was initiated about 600 feet past the runway threshold and about 35 feet agl. During the flare, the ground track achieved the centerline, but deviated back to the left before main gear touchdown, which occurred about 3,200 feet past the runway threshold. At touchdown, the left main gear was about 56 feet left of centerline with an airplane ground track of about 5 degrees to the left. Within 2 seconds of touchdown (about 300 feet of travel), the left main gear crossed the white runway edge strip, and within 5 seconds of touchdown (about 1,000 feet of travel), the left main gear departed the paved surface. A nearly full right rudder input was made at about 3,450 feet from the runway threshold after main gear touchdown. The airplane departed the runway surface before the ground track altered back to the right. The company's Operations Manual states, "Control Glidepath so that touchdown occurs on the 1000 foot point (Fixed Distance Marker)...If an unsatisfactory approach is likely to result in a long landing, GO AROUND and make a second approach."

Probable cause

The second in command failed to maintain proper runway alignment, directional control, and landed long. The pilot in command failed to execute a go-around and failed to provide adequate supervision. Additional factors included the thunderstorm, the dark night, the muddy terrain, and the FODed engines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI01FA292
Event ID
20010830X01825
Case number
CHI01FA292
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: 86cd344cd8dc2dcbb01c6ddceb843e03ee5ae2757b56570e99cede44beacf37f; retrieved 2026-09-18T16:10:09.327Z.
  • The NTSB's operator name is blank for N306AW; the operator shown is the name the NTSB's other records give its FAA operator code, AWXA.