# Incident 20060826023619I: Airbus A319132, Baltimore, MD, August 26, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 26, 2006, 18:42 local time
- Place: Baltimore, MD
- Airport: Baltimore-Washington International
- Phase of flight: Climb
- Operating rules: Air carrier (Part 121)
- Operator: AWXA
- Location: 39.2904° N, 76.6122° W: Placed by OpenAirDocs: center of Baltimore, MD, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.2904&lon=-76.6122&mi=10
- Aircraft: N808AW, registered now (https://openairdocs.org/aircraft/N808AW) (OpenAirDocs)
- Registry model: Airbus Industrie A319-132 (registry code 3930340, https://openairdocs.org/model/airbus-industrie-a319-132) (OpenAirDocs)
- Registry engine: IAE V2500SERIES (registry code 34601, https://openairdocs.org/engine/iae-v2500series) (OpenAirDocs)
- Reported make and model: AIRBUS A319132
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060826023619I

## Narrative

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

(-23) PASSENGER ^PRIVACY DATA OMITTED^ CREATED A DISTURBANCE BECOMING PHYSICALLY ABUSIVE TO CABIN CREW AND OTHER PASSENGERS CAUSING THE FLIGHT TO RETURN TO FIELD. THE CABIN CREW CLASSIFIED THIS AS LEVEL III THREAT.

## Other reports on N808AW (2)

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

- [Accident 20120414012209A](https://openairdocs.org/incident/20120414012209A), Apr 14, 2012: Airbus Industrie A319-132 (N808AW), Denver, CO, No damage. Aircraft started descent from flight level 390 where the ride had been smooth. The seat belt sign was on for the descent. Approaching flight level 320 the…
- [Incident 20000712036029I](https://openairdocs.org/incident/20000712036029I), Jul 12, 2000: Airbus A319132 (N808AW), Omaha, NE. (-23)N808AW, A-319, being operated as American west airlines flight 784, was enroute from phoenix, AZ, to columbus, OH, when the pilot diverted to Omaha, NE,…

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.