B737 first officer exceeded crew maximum duty time.

Attributes
ACN	424010
Time
Date	199812
Day	Thu
Local Time Of Day	0001 To 0600
Place
Locale Reference	atc facility : phx
State Reference	AZ
Altitude	msl bound lower : 35000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Navigation In Use	Other
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : commercial pilot : instrument
Experience	flight time last 90 days : 350 flight time total : 14000 flight time type : 5000
ASRS Report	424010
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence other other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

While on trip pairing abcd, day #2, irregular operations were in progress because of an ice storm. We were rerted and remained overnight in mco instead of roc. Our company had just instituted a new computer system. Crews and airplanes were being rerted everywhere along with crews. We went from mco-phl and deadheaded from phl-pit and my crew left me in pit. I was advised by scheduling to continue on with my original pairing. I picked up a new captain and flight attendant crew (partially). We kept waiting for the other flight attendants to arrive. About that time we got word to change aircraft with another crew. So between preflting several aircraft, switching crews and flts from my original pairing, a winter storm and changing crews, aircraft and flts, I simply lost track of time. Plus, due to very strong winter jet stream winds, the long flight to phx took almost another hour than originally projected. The problem arose through irregular operations. Many variables compounded because of the above listed factors, plus the new crew scheduling computer instituted. I discovered the crew duty day problem when I started adding up my time the next day on the leg back. Better vigilance on my part and crew scheduling, bad WX and computer changeovers. Being rerted and not having a printout didn't help me be aware of crew duty period during periods of high workload.

Original NASA ASRS Text

Title: B737 FO EXCEEDED CREW MAX DUTY TIME.

Narrative: WHILE ON TRIP PAIRING ABCD, DAY #2, IRREGULAR OPS WERE IN PROGRESS BECAUSE OF AN ICE STORM. WE WERE RERTED AND REMAINED OVERNIGHT IN MCO INSTEAD OF ROC. OUR COMPANY HAD JUST INSTITUTED A NEW COMPUTER SYS. CREWS AND AIRPLANES WERE BEING RERTED EVERYWHERE ALONG WITH CREWS. WE WENT FROM MCO-PHL AND DEADHEADED FROM PHL-PIT AND MY CREW LEFT ME IN PIT. I WAS ADVISED BY SCHEDULING TO CONTINUE ON WITH MY ORIGINAL PAIRING. I PICKED UP A NEW CAPT AND FLT ATTENDANT CREW (PARTIALLY). WE KEPT WAITING FOR THE OTHER FLT ATTENDANTS TO ARRIVE. ABOUT THAT TIME WE GOT WORD TO CHANGE ACFT WITH ANOTHER CREW. SO BTWN PREFLTING SEVERAL ACFT, SWITCHING CREWS AND FLTS FROM MY ORIGINAL PAIRING, A WINTER STORM AND CHANGING CREWS, ACFT AND FLTS, I SIMPLY LOST TRACK OF TIME. PLUS, DUE TO VERY STRONG WINTER JET STREAM WINDS, THE LONG FLT TO PHX TOOK ALMOST ANOTHER HR THAN ORIGINALLY PROJECTED. THE PROB AROSE THROUGH IRREGULAR OPS. MANY VARIABLES COMPOUNDED BECAUSE OF THE ABOVE LISTED FACTORS, PLUS THE NEW CREW SCHEDULING COMPUTER INSTITUTED. I DISCOVERED THE CREW DUTY DAY PROB WHEN I STARTED ADDING UP MY TIME THE NEXT DAY ON THE LEG BACK. BETTER VIGILANCE ON MY PART AND CREW SCHEDULING, BAD WX AND COMPUTER CHANGEOVERS. BEING RERTED AND NOT HAVING A PRINTOUT DIDN'T HELP ME BE AWARE OF CREW DUTY PERIOD DURING PERIODS OF HIGH WORKLOAD.

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.