20110930025369I

Incident · Minor damage

FAA incident report · Bombardier CL-600-2B19 · Philadelphia, PA · September 30, 2011

Date
September 30, 2011 · 17:09 local
Place
Philadelphia, PA
Airport
Philadelphia Itl
Phase of flight
Descent
Operating rules
Air carrier (Part 121)
Operator
VNAA
Damage
Minor damage
Aircraft
N256PS
Reported as
Bombardier CL-600-2B19
Reported engine
GE CF34 series
People aboard
52
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Airline transport
Pilot’s flight hours
7,369 total6,176 in this make and model240 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.