DA20 cargo aircraft had engine flameout just prior to leveloff. Flight crew requested lower altitude...

Attributes
ACN	383222
Time
Date	199710
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : zzz
State Reference	US
Altitude	msl bound lower : 34900 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	artcc : zzz
Operator	common carrier : air carrier
Make Model Name	Falcon 20FJF/20C/20D/20E/20F
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 135 flight time total : 5000 flight time type : 450
ASRS Report	383222
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	aircraft equipment problem : critical
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : declared emergency flight crew : overcame equipment problem
Consequence	Other
Supplementary
Primary Problem	Aircraft

Narrative:

Climbing to cruise (FL350) at FL349 encountered light turbulence just prior to leveloff. Engine flamed out at FL349. Captain idented, PNF first officer verified engine. First officer began calling checklist for securing engine. Captain PF secured engine. Captain stated need for lower altitude -- requested. First officer let him make ATC call. Captain requested lower, informing ATC this was due to pressurization problem. At FL280 air start checklist was initiated and engine started. All system normal. Once all checklists were completed, I advised captain that we needed to be certain that necessary reports, misrs and mirrs were completed. Captain agreed and thanked me for reminding him of this. We deplaned in okc, reviewing that the captain would make appropriate calls. After some time and a couple of calls, captain said he was awaiting further information. Captain re-emerged to state that the director of maintenance felt that no write-ups were required as the aircraft had flamed out due to 'atmospheric conditions,' nothing mechanical. We were free to continue the trip. I inquired again whether a report was required and was told the dom said no. We continued on to mmho with no write-ups and unbeknownst to me, without contacting flight operations to report the incident. I assumed that with so many calls made, operations must have been notified -- it was not. In review, my prompting captain about reports was insufficient. Due to lateness of hour, he became fixated, I believe, on these 2 items (and writing up failure in logbook). Notifying flight operations was left by the wayside. Operations certainly would have pointed out our failure to write up aircraft and ground it appropriately. The dom and captain were incorrectly focused on engine system operation and not regulation 135/121 flight operations requirements. I needed to be more aggressive and certain that the big picture had been addressed, and not merely the mechanical aspects. We were not, after all, mechanics, but pilots. We should not have continued this flight.

Original NASA ASRS Text

Title: DA20 CARGO ACFT HAD ENG FLAMEOUT JUST PRIOR TO LEVELOFF. FLC REQUESTED LOWER ALT AND RESTARTED THE ENG. RPTR FO FAULTS CAPT AND MAINT FOR NOT WRITING UP THE MALFUNCTION AND CONTINUING TO FLY THE ACFT.

Narrative: CLBING TO CRUISE (FL350) AT FL349 ENCOUNTERED LIGHT TURB JUST PRIOR TO LEVELOFF. ENG FLAMED OUT AT FL349. CAPT IDENTED, PNF FO VERIFIED ENG. FO BEGAN CALLING CHKLIST FOR SECURING ENG. CAPT PF SECURED ENG. CAPT STATED NEED FOR LOWER ALT -- REQUESTED. FO LET HIM MAKE ATC CALL. CAPT REQUESTED LOWER, INFORMING ATC THIS WAS DUE TO PRESSURIZATION PROB. AT FL280 AIR START CHKLIST WAS INITIATED AND ENG STARTED. ALL SYS NORMAL. ONCE ALL CHKLISTS WERE COMPLETED, I ADVISED CAPT THAT WE NEEDED TO BE CERTAIN THAT NECESSARY RPTS, MISRS AND MIRRS WERE COMPLETED. CAPT AGREED AND THANKED ME FOR REMINDING HIM OF THIS. WE DEPLANED IN OKC, REVIEWING THAT THE CAPT WOULD MAKE APPROPRIATE CALLS. AFTER SOME TIME AND A COUPLE OF CALLS, CAPT SAID HE WAS AWAITING FURTHER INFO. CAPT RE-EMERGED TO STATE THAT THE DIRECTOR OF MAINT FELT THAT NO WRITE-UPS WERE REQUIRED AS THE ACFT HAD FLAMED OUT DUE TO 'ATMOSPHERIC CONDITIONS,' NOTHING MECHANICAL. WE WERE FREE TO CONTINUE THE TRIP. I INQUIRED AGAIN WHETHER A RPT WAS REQUIRED AND WAS TOLD THE DOM SAID NO. WE CONTINUED ON TO MMHO WITH NO WRITE-UPS AND UNBEKNOWNST TO ME, WITHOUT CONTACTING FLT OPS TO RPT THE INCIDENT. I ASSUMED THAT WITH SO MANY CALLS MADE, OPS MUST HAVE BEEN NOTIFIED -- IT WAS NOT. IN REVIEW, MY PROMPTING CAPT ABOUT RPTS WAS INSUFFICIENT. DUE TO LATENESS OF HR, HE BECAME FIXATED, I BELIEVE, ON THESE 2 ITEMS (AND WRITING UP FAILURE IN LOGBOOK). NOTIFYING FLT OPS WAS LEFT BY THE WAYSIDE. OPS CERTAINLY WOULD HAVE POINTED OUT OUR FAILURE TO WRITE UP ACFT AND GND IT APPROPRIATELY. THE DOM AND CAPT WERE INCORRECTLY FOCUSED ON ENG SYS OP AND NOT REG 135/121 FLT OPS REQUIREMENTS. I NEEDED TO BE MORE AGGRESSIVE AND CERTAIN THAT THE BIG PICTURE HAD BEEN ADDRESSED, AND NOT MERELY THE MECHANICAL ASPECTS. WE WERE NOT, AFTER ALL, MECHS, BUT PLTS. WE SHOULD NOT HAVE CONTINUED THIS FLT.

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.

DA20 cargo aircraft had engine flameout just prior to leveloff. Flight crew requested lower altitude and restarted the engine. Reporter first officer faults captain and maintenance for not writing up the malfunction and continuing to fly the aircraft.