A CL65 flight crew departed their aircraft with an engine running while parked at the gate at roa.

Attributes
ACN	482660
Time
Date	200008
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : roa.airport
State Reference	VA
Altitude	agl single value : 0
Environment
Light	Night
Aircraft 1
Controlling Facilities	tower : okc.tower
Operator	common carrier : air carrier
Make Model Name	Challenger CL604
Operating Under FAR Part	Part 121
Flight Phase	ground : parked
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : atp
Experience	flight time last 90 days : 250 flight time total : 13000 flight time type : 250
ASRS Report	482660
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : multi engine
Events
Anomaly	non adherence : company policies other anomaly other
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

During engine shutdown at the gate, the right engine was not shut down and the crew left the aircraft. Our company uses single engine taxi-in procedures in which the left engine is shut down while taxiing in. Once in the gate with chocks in, the crew is directed to start automatically initiated shutdown flows, part of which directs the captain to shut down the right engine. My flow was somehow interrupted and the engine was not shut down. All flows are backed by written checklists, but the checklist was never performed. I believe because of the way the checklist is written we both thought the other had done it. All checklists indicate who will perform them, except the shutdown from the line. This led both pilots to believe the other was performing the checklist. Compounding the problem is the fact that the from-the-line checklist is a silent checklist, so neither pilot was expecting to hear anything. The final problem is there is no direction from the flight standards manual as to whom will perform the shutdown checklist.

Original NASA ASRS Text

Title: A CL65 FLC DEPARTED THEIR ACFT WITH AN ENG RUNNING WHILE PARKED AT THE GATE AT ROA.

Narrative: DURING ENG SHUTDOWN AT THE GATE, THE R ENG WAS NOT SHUT DOWN AND THE CREW LEFT THE ACFT. OUR COMPANY USES SINGLE ENG TAXI-IN PROCS IN WHICH THE L ENG IS SHUT DOWN WHILE TAXIING IN. ONCE IN THE GATE WITH CHOCKS IN, THE CREW IS DIRECTED TO START AUTOMATICALLY INITIATED SHUTDOWN FLOWS, PART OF WHICH DIRECTS THE CAPT TO SHUT DOWN THE R ENG. MY FLOW WAS SOMEHOW INTERRUPTED AND THE ENG WAS NOT SHUT DOWN. ALL FLOWS ARE BACKED BY WRITTEN CHKLISTS, BUT THE CHKLIST WAS NEVER PERFORMED. I BELIEVE BECAUSE OF THE WAY THE CHKLIST IS WRITTEN WE BOTH THOUGHT THE OTHER HAD DONE IT. ALL CHKLISTS INDICATE WHO WILL PERFORM THEM, EXCEPT THE SHUTDOWN FROM THE LINE. THIS LED BOTH PLTS TO BELIEVE THE OTHER WAS PERFORMING THE CHKLIST. COMPOUNDING THE PROB IS THE FACT THAT THE FROM-THE-LINE CHKLIST IS A SILENT CHKLIST, SO NEITHER PLT WAS EXPECTING TO HEAR ANYTHING. THE FINAL PROB IS THERE IS NO DIRECTION FROM THE FLT STANDARDS MANUAL AS TO WHOM WILL PERFORM THE SHUTDOWN CHKLIST.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.