# Incident 20110930025369I: Bombardier Inc CL-600-2B19, Philadelphia, PA, September 30, 2011

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: September 30, 2011, 17:09 local time
- Place: Philadelphia, PA
- Airport: Philadelphia Itl
- Damage: Minor damage
- Phase of flight: Descent
- Operating rules: Air carrier (Part 121)
- Operator: VNAA
- Location: 39.9523° N, 75.1638° W: Placed by OpenAirDocs: center of Philadelphia, PA, within about 7 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=39.9523&lon=-75.1638&mi=10
- Aircraft: N256PS, a cancelled registration (https://openairdocs.org/deregistered/N256PS-2025-02-26) (OpenAirDocs)
- Registry model: Bombardier CL-600-2B19 (registry code 1390008, https://openairdocs.org/model/bombardier-cl-600-2b19) (OpenAirDocs)
- Registry engine: GE CF34 series (registry code 30015, https://openairdocs.org/engine/ge-cf34-series) (OpenAirDocs)
- Reported make and model: BOMBARDIER INC CL-600-2B19
- Reported engine: GE CF34 SERIES
- People aboard: 52
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport
- Pilot flight hours: 7,369 total, 6,176 in this make and model, 240 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110930025369I

## Narrative

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

UPON DESCENT INTO PHL FROM TYS, THE FLIGHT ATTENDANT AND MID-CABIN PASSENGERS SMELLED AN ELECTRICAL BURNING SMELL.  THE FLIGHT CREW DECLARED AN EMERGENCY, LANDED SAFELY ON RUNWAY 35, PROCEEDED ON TAXIWAY K-3, AND INITIATED AN EMERGENCY EVACUATION THROUGH THE TWO OVERWING EMERGENCY EXIT DOORS AND CABIN DOOR.  THERE WERE NO INJURIES.  ADDITIONAL NARRATIVE AS PER 8020.11C, CHAPTER 5, SECTION 2, PARAGRAPH 11, PAGES 5-8 AND 5-9:  9-30-11/PHL/PSA AIRLINES/N256PS/CL600/#25881.  REASON FOR EVACUATION:  STRONG ODOR, ELECTRICAL SMELL/FUMES IN THE GALLEY AND ROWS 10-13 UPON DESCENT INTO PHL. CREW DECLARED AN IN-FLIGHT EMERGENCY AND PERFORMED A PRECAUTIONARY EVACUATION. 2.  WHO INITIATED THE EVACUATION?THE CAPTAIN.3.  WHICH EXITS (BY SPECIFIC LOCATION) WERE USED, WHICH EXITS WERE NOT USED, AND REASON FOR NONUSE:  THE TWO OVERWING EMERGENCY EXITS AND THE CABIN DOOR.4.  WHETHER ANY EXITS, SLIDES, OR ASSOCIATED COMPONENTS MALFUNCTIONED AND, IF SO, WHAT WERE THE MALFUNCTIONS:  NO MALFUNCTIONS. THE OVERWING EXITS OPERATED PROPERLY WHEN OPENED, BUT WERE DAMAGED WHEN THROWN THROUGH THE OPENING FOR EGRESS FROM THE AIRCRAFT.5.  WHETHER ANY PARTICULAR EXIT WAS USED BY THE MAJORITY OF THE EVACUEES AND, IF SO, THE APPARENT REASON:  AS DIRECTED BY THE CREW, BOTH OVERWING EMERGENCY EXITS WERE PRIMARILY USED BY PASSENGERS.6.  THE ESTIMATED TOTAL TIME IT TOOK TO EVACUATE THE AIRCRAFT:  TWO MINUTES.7.  NATURE AND EXTENT OF INJURIES:  NONE.

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.