# Incident 20001116039439I: Boeing 737347, Colorado Spring, CO, November 16, 2000

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: November 16, 2000, 22:12 local time
- Place: Colorado Spring, CO
- Airport: City Of Colorado Springs Municipal
- Phase of flight: Final Approach
- Operating rules: Air carrier (Part 121)
- Operator: DALA
- Location: 38.8058° N, 104.7008° W: Placed by OpenAirDocs at CITY OF COLORADO SPRINGS MUNI (COS), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.8058&lon=-104.7008&mi=10
- Aircraft: N306WA, a cancelled registration (https://openairdocs.org/deregistered/N306WA-2007-05-04) (OpenAirDocs)
- Registry model: Boeing 737-347 (registry code 138447U, https://openairdocs.org/model/boeing-737-347) (OpenAirDocs)
- Registry engine: CFM International CFM56 series (registry code 13802, https://openairdocs.org/engine/cfm-international-cfm56-series) (OpenAirDocs)
- Reported make and model: BOEING 737347
- People aboard: 60
- Fatal injuries: 0
- Pilot flight hours: 11,000 total, 3,234 in this make and model, 128 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001116039439I

## Narrative

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

(-23) INM0300102-EMERGENCY DECLARED DURING LANDING AT COS. BOTH GENERATORS FAILED. UNABLE TO RESET. A/C LANDED ON BATTERY POWER. APU START NOT ATTEMPTED. AFTER LANDING FIRE MARSHALLS CONDUCTED EXTERIOR CHECK AT REQUEST OF CPT. NOTHING FOUND. AFTER LANDING AND DURING CHECK CABIN CREW (3) REPORTED SMOKE IN CABIN. EMERGENCY EVAC CONSIDERED BUT NOT CONDUCTED. SMOKE DISIPATED AND CPT ELECTED TO TAXI TO THE GATE. PASSENGERS DEPLANED WITHOUT INCIDENT. BOTH CPT AND F/O STATEMENTS DO NOT INDICATE ANY SMOKE WAS REPORTED BY CABIN CREW. DENVER MTC INSPECTED A/C AND PERFORMED MAINTENANCE. SHIP NO. 206, LOG NO. C841089, CONTROL NO. 841089001.

## Other reports on N306WA (5)

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

- [Incident 19980915033689I](https://openairdocs.org/incident/19980915033689I), Sep 15, 1998: Boeing 737* (N306WA), Salt Lake City, UT. -23 After reviewing the capt statement and confirming his description of t he incident with ATC and fss in cdc, it is concluded this incident occurred while…
- [Incident 19890727047939I](https://openairdocs.org/incident/19890727047939I), Jul 27, 1989: Boeing 737347 (N306WA), Jackson, WY, Minor damage. Aircraft ran off end of runway during landing. Rubber build up on last part of runway.
- [Incident 19890606040909I](https://openairdocs.org/incident/19890606040909I), Jun 6, 1989: Boeing 737347 (N306WA), Buffalo, NY. Airframe vibrations on takeoff. Returned. Found problem with pressurization system. Replaced flow control valve.
- [Incident 19870813056479I](https://openairdocs.org/incident/19870813056479I), Aug 13, 1987: Boeing 737347 (N306WA), Milford, UT. The aircraft encountered clear air turbulence during descent. One passenger injured.
- [Incident 19860201004089I](https://openairdocs.org/incident/19860201004089I), Feb 1, 1986: Boeing 737347 (N306WA), Omaha, NE. During start attempt after pushback engine backfired and would not start. Engine to be changed.

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.