Narrative:

After block out; we started engines and began to taxi out. As the first officer; re engaged the packs; the right pack begin flickering on and off which also resulted in an EICAS message coming on and off. During taxi; the right pack eventually stayed off. We have a new procedure here at the air carrier which allows us pilots to defer a maintenance item if it is an MEL item. It is a fairly new procedure that we never received training on. It was simply sent out in a bulletin by our chief pilot putting the procedure in place. I was not familiar with the procedure and I advised both the first officer and captain that I did not have the bulletin on me and if they were familiar. They advised that they were not and to contact maintenance control to see if it is indeed an item that we can defer and if we are able to do so. I called dispatch who eventually conferenced in maintenance control. The maintenance controller advised that we are able to defer the item under the new procedures and proceeded to give us instruction on a couple of ways to try and reset the item and after no success; how to enter the item in the aircraft maintenance logbook. He eventually gave us his name to put on the log page. We then had the dispatcher update our flight plan to reflect the change and gave us her name to place on the amended flight plan. We deferred the item according the maintenance controllers instructions and proceeded to depart with only one pack and no further irregularities. During the flight; the first officer remembered he had the bulletin on his laptop and opened it up to review it. After reading the bulletin; we only then realized; that the bulletin was only valid for our company 757's and had not yet been approved for our company 767's; though the company was waiting on FAA approval for them. Had we had the bulletins in the cockpit; or had company issued laptops that included these bulletins; we would have been able to catch this issue prior to taking off.

Google
 

Original NASA ASRS Text

Title: A B767-300 crew MEL'ed an inoperative Pack during taxi but a FAA procedure allowing Flight Crew MEL actions was not yet in place for the B767.

Narrative: After block out; we started engines and began to taxi out. As the First Officer; re engaged the PACKS; the right PACK begin flickering on and off which also resulted in an EICAS message coming on and off. During taxi; the Right Pack eventually stayed off. We have a new procedure here at the Air Carrier which allows us pilots to defer a maintenance item if it is an MEL item. It is a fairly new procedure that we never received training on. It was simply sent out in a bulletin by our Chief Pilot putting the procedure in place. I was not familiar with the procedure and I advised both the First Officer and Captain that I did not have the bulletin on me and if they were familiar. They advised that they were not and to contact Maintenance Control to see if it is indeed an item that we can defer and if we are able to do so. I called Dispatch who eventually conferenced in Maintenance Control. The Maintenance Controller advised that we are able to defer the item under the new procedures and proceeded to give us instruction on a couple of ways to try and reset the item and after no success; how to enter the item in the aircraft maintenance logbook. He eventually gave us his name to put on the log page. We then had the Dispatcher update our flight plan to reflect the change and gave us her name to place on the amended flight plan. We deferred the item according the Maintenance Controllers instructions and proceeded to depart with only one pack and no further irregularities. During the flight; the First Officer remembered he had the bulletin on his laptop and opened it up to review it. After reading the bulletin; we only then realized; that the bulletin was only valid for our company 757's and had not yet been approved for our company 767's; though the company was waiting on FAA approval for them. Had we had the bulletins in the cockpit; or had Company issued laptops that included these bulletins; we would have been able to catch this issue prior to taking off.

Data retrieved from NASA's ASRS site as of April 2012 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.