# Incident 20020917026659I: Boeing 737790, Seattle, WA, September 17, 2002

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 17, 2002, 00:34 local time
- Place: Seattle, WA
- Airport: Seattle-Tacoma International
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Operator: ASAA
- Location: 47.4499° N, 122.3118° W: Placed by OpenAirDocs at SEATTLE-TACOMA INTL (SEA), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=47.4499&lon=-122.3118&mi=10
- Aircraft: N619AS, registered now (https://openairdocs.org/aircraft/N619AS) (OpenAirDocs)
- Registry model: Boeing 737-790 (registry code 13844CN, https://openairdocs.org/model/boeing-737-790) (OpenAirDocs)
- Registry engine: CFM International CFM56 series (registry code 13802, https://openairdocs.org/engine/cfm-international-cfm56-series) (OpenAirDocs)
- Reported make and model: BOEING 737790
- People aboard: 12
- Fatal injuries: 0
- Pilot flight hours: 16,100 total, 7,692 in this make and model, 33 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020917026659I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) ALASKA AIRLINES, INC. FAILED TO HAVE ADEQUATE PROCEDURES IN PLACE, PRIOR TO LANDING, TO INSURE THAT THE GALLEY CARTS WERE/ARE SECURE. AS A RESULT, THE FLIGHT CREW FAILED TO INSURE THAT THE BRAKES WERE SET, AND THE LOCKING LEVERS WERE PROPERLY LATCHED ON THE CENTER REAR GALLEY CART.

## Other reports on N619AS (1)

Matched to the same aircraft by N-number and date.

- [Incident 20050221006359I](https://openairdocs.org/incident/20050221006359I), Feb 21, 2005: Boeing 737790 (N619AS), Fairbanks, AK. (-23) On 2-21-2005, at 1931 local Alaska time, Alaska airlines flight 127 landed at the Fairbanks International Airport on runway 1L. While turning onto…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
