<< >> NASA ASRS Report 608168, February 2004

B767-300 crew did not get a dispatch release at the redispatch re-release point. Flight crew management did not record the point on the master flight plan.

Attributes
ACN	608168
Time
Date	200402
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : czul.artcc
State Reference	PQ
Altitude	msl single value : 35000
Aircraft 1
Controlling Facilities	artcc : czul.artcc
Operator	common carrier : air carrier
Make Model Name	B767 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	608168
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : company policies non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	flight crew : became reoriented other
Consequence	other Other
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance

Narrative:

Flight was released to cyul with re-release planned for over rodbo intersection. We had just come ashore. I had checked the north american route. Flight was running ahead of time and fuel. The first officer had just returned from his break. Before going on my break, I briefed him on current status, possible emergency (on fire) landing sites plus other not so critical landing fields. 'Did we get the re-release' he says. Completely brain-deaded it. We were 15 mins past rodbo. Immediately messaged dispatch then called on satcom. Dispatcher said his previous shift had not informed him of re-release. He sent re-release a few mins later and we proceeded to ord. A robotic divert to cyul did not seem to make any sense. It has gotten me thinking about how to better flag this event. I hope dispatch will be doing some similar thinking.

Related reports:

• MD11F flight crew on an international flight with a redispat...
• B747-400 flight crew receives the wrong re-dispatch fix; con...
• B747 first officer reported arriving at their re-dispatch po...
• B747-400 crew did not have the required fuel at the redispat...
• B777 first officers report not detecting that a revised rele...
• An air carrier flight crew flying B747-100 to ymml fails to ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: B767-300 CREW DID NOT GET A DISPATCH RELEASE AT THE REDISPATCH RE-RELEASE POINT. FLT CREW MGMNT DID NOT RECORD THE POINT ON THE MASTER FLT PLAN.

Narrative: FLT WAS RELEASED TO CYUL WITH RE-RELEASE PLANNED FOR OVER RODBO INTXN. WE HAD JUST COME ASHORE. I HAD CHKED THE NORTH AMERICAN RTE. FLT WAS RUNNING AHEAD OF TIME AND FUEL. THE FO HAD JUST RETURNED FROM HIS BREAK. BEFORE GOING ON MY BREAK, I BRIEFED HIM ON CURRENT STATUS, POSSIBLE EMER (ON FIRE) LNDG SITES PLUS OTHER NOT SO CRITICAL LNDG FIELDS. 'DID WE GET THE RE-RELEASE' HE SAYS. COMPLETELY BRAIN-DEADED IT. WE WERE 15 MINS PAST RODBO. IMMEDIATELY MESSAGED DISPATCH THEN CALLED ON SATCOM. DISPATCHER SAID HIS PREVIOUS SHIFT HAD NOT INFORMED HIM OF RE-RELEASE. HE SENT RE-RELEASE A FEW MINS LATER AND WE PROCEEDED TO ORD. A ROBOTIC DIVERT TO CYUL DID NOT SEEM TO MAKE ANY SENSE. IT HAS GOTTEN ME THINKING ABOUT HOW TO BETTER FLAG THIS EVENT. I HOPE DISPATCH WILL BE DOING SOME SIMILAR THINKING.

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.