37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 378832 |
Time | |
Date | 199708 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : pit |
State Reference | PA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | A310 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : takeoff ground : preflight ground other : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 20 flight time total : 6500 flight time type : 210 |
ASRS Report | 378832 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : far other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Chart Or Publication |
Air Traffic Incident | other |
Narrative:
This letter describes the circumstances that could have possibly led me to unintentionally exceed the far 121.505 duty time requirements (ie, 16 hour duty day). After evaluating my actual duty for the time in question (aug/xa/97 and aug/xb/97), I believe that I was just under the 16 hour limit. However, I found several factors worthy of this report. I was scheduled to continue that morning as first officer on flight (mem-pit-yyz). Upon arrival at pit, the A300 suffered a mechanical (hydraulic leak to the aft lower cargo door) which grounded the aircraft. Eventually, the company diverted another aircraft with the intention of my crew taking the new aircraft to yyz. As the day progressed and I realized that my duty time was becoming critical, I phoned crew scheduling and made them aware of my situation and asked them to verify my limits. I was busy preparing the aircraft for departure so I asked them to call us via radio or ACARS if there was going to be a problem. Due to several factors, the captain and I estimated that we could still make yyz prior to exceeding my duty limits which we conservatively figured at XQ22Z (using scheduled show time the previous night at iah instead of actual show). As stated earlier, the actual show was approximately XA25Z, which gave us a slight buffer (3 mins). Additionally, we estimated that we could save additional time. Not receiving any word to the contrary from company dispatch, we blocked out. The taxi at pit went as planned. Approximately 5 mins after takeoff, we received an ACARS message from the company requesting us to make contact via atl radio. I initiated the call. Flight control wanted to know if we could block in prior to XP52Z. I informed them that we estimated that we could meet that requirement. However, upon arrival at yyz, the runway in use had changed to runway 15L. This runway was the worst possible runway for us. Not only would we have to overfly the airport in order to fly the approach, but the taxi route was significantly longer. We blocked in at XP55Z, thus, following the allowed 30 min debrief period, putting me right at 16HRS of duty. So, what are the issues that concern me following this incident? Let me start by stating that a crew member in the field does not have the time to scrutinize in minute detail issues such as duty limits when he/she is trying to get an aircraft ready for flight, especially when time is critical. Support in such areas should come from the company where someone is behind a computer screen with access to all the information. Nobody informed us of any possible duty limit problems, even though we were in pit, broke, for over 6 hours. I was the one who informed them. Crew scheduling has the capability to provide the crew with a duty break (if the known delay is to be over 2 hours) in order to 'insure future legality.' that duty break was never offered and we were in pit for over 6 hours. Again, is it my job out there on the line to monitor such issues? I called the company approximately 10 mins prior to blockout and told them to investigate the situation. I was too busy at that time trying to complete my duties in preparation for departure. It took approximately 22-25 mins for them to contact us. We were well on our way by then. Far 121.505 states that the maximum duty limit is 16 hours, however, it provides no guidance (that I could find) as to if that is scheduled duty time or actual time. It implies actual time. In that case, where is the guidance covering sits where your flight is planned to meet duty limits but due to ATC delays, WX, etc, you exceed those limits? The fch states that no flight may depart if it will exceed the duty limits. Again, what happens if you don't plan on exceeding them but due to unexpected delays you do exceed limits? It is better to anticipate a duty limit problem than to push the limits. Far 121.505 could better define sits such as that experienced above. Can you block out with the intention of meeting the 16 hour duty limit and once en route, exceed 16 hours due to unanticipated delays? In conclusion, this situation placed an unnecessary burden on the flight crew. Since the 'big picture' is maintained by the company dispatchers, they need to take a commanding role in determining when duty breaks are justified.
Original NASA ASRS Text
Title: AIRLINE FO QUESTIONS THE INTERP OF THE FAR PERTAINING TO DUTY TIMES VERSUS FLT TIMES. SAYS THE INTERP IS VAGUE. HAS A PROB WITH HIS AIRLINE'S SCHEDULING DISPATCH DEPT THAT DOES NOT FOLLOW THEIR CREWS CLOSELY ENOUGH TO INSURE COMPLIANCE WITH THE 16 HR DUTY RULES.
Narrative: THIS LETTER DESCRIBES THE CIRCUMSTANCES THAT COULD HAVE POSSIBLY LED ME TO UNINTENTIONALLY EXCEED THE FAR 121.505 DUTY TIME REQUIREMENTS (IE, 16 HR DUTY DAY). AFTER EVALUATING MY ACTUAL DUTY FOR THE TIME IN QUESTION (AUG/XA/97 AND AUG/XB/97), I BELIEVE THAT I WAS JUST UNDER THE 16 HR LIMIT. HOWEVER, I FOUND SEVERAL FACTORS WORTHY OF THIS RPT. I WAS SCHEDULED TO CONTINUE THAT MORNING AS FO ON FLT (MEM-PIT-YYZ). UPON ARR AT PIT, THE A300 SUFFERED A MECHANICAL (HYD LEAK TO THE AFT LOWER CARGO DOOR) WHICH GNDED THE ACFT. EVENTUALLY, THE COMPANY DIVERTED ANOTHER ACFT WITH THE INTENTION OF MY CREW TAKING THE NEW ACFT TO YYZ. AS THE DAY PROGRESSED AND I REALIZED THAT MY DUTY TIME WAS BECOMING CRITICAL, I PHONED CREW SCHEDULING AND MADE THEM AWARE OF MY SIT AND ASKED THEM TO VERIFY MY LIMITS. I WAS BUSY PREPARING THE ACFT FOR DEP SO I ASKED THEM TO CALL US VIA RADIO OR ACARS IF THERE WAS GOING TO BE A PROB. DUE TO SEVERAL FACTORS, THE CAPT AND I ESTIMATED THAT WE COULD STILL MAKE YYZ PRIOR TO EXCEEDING MY DUTY LIMITS WHICH WE CONSERVATIVELY FIGURED AT XQ22Z (USING SCHEDULED SHOW TIME THE PREVIOUS NIGHT AT IAH INSTEAD OF ACTUAL SHOW). AS STATED EARLIER, THE ACTUAL SHOW WAS APPROX XA25Z, WHICH GAVE US A SLIGHT BUFFER (3 MINS). ADDITIONALLY, WE ESTIMATED THAT WE COULD SAVE ADDITIONAL TIME. NOT RECEIVING ANY WORD TO THE CONTRARY FROM COMPANY DISPATCH, WE BLOCKED OUT. THE TAXI AT PIT WENT AS PLANNED. APPROX 5 MINS AFTER TKOF, WE RECEIVED AN ACARS MESSAGE FROM THE COMPANY REQUESTING US TO MAKE CONTACT VIA ATL RADIO. I INITIATED THE CALL. FLT CTL WANTED TO KNOW IF WE COULD BLOCK IN PRIOR TO XP52Z. I INFORMED THEM THAT WE ESTIMATED THAT WE COULD MEET THAT REQUIREMENT. HOWEVER, UPON ARR AT YYZ, THE RWY IN USE HAD CHANGED TO RWY 15L. THIS RWY WAS THE WORST POSSIBLE RWY FOR US. NOT ONLY WOULD WE HAVE TO OVERFLY THE ARPT IN ORDER TO FLY THE APCH, BUT THE TAXI RTE WAS SIGNIFICANTLY LONGER. WE BLOCKED IN AT XP55Z, THUS, FOLLOWING THE ALLOWED 30 MIN DEBRIEF PERIOD, PUTTING ME RIGHT AT 16HRS OF DUTY. SO, WHAT ARE THE ISSUES THAT CONCERN ME FOLLOWING THIS INCIDENT? LET ME START BY STATING THAT A CREW MEMBER IN THE FIELD DOES NOT HAVE THE TIME TO SCRUTINIZE IN MINUTE DETAIL ISSUES SUCH AS DUTY LIMITS WHEN HE/SHE IS TRYING TO GET AN ACFT READY FOR FLT, ESPECIALLY WHEN TIME IS CRITICAL. SUPPORT IN SUCH AREAS SHOULD COME FROM THE COMPANY WHERE SOMEONE IS BEHIND A COMPUTER SCREEN WITH ACCESS TO ALL THE INFO. NOBODY INFORMED US OF ANY POSSIBLE DUTY LIMIT PROBS, EVEN THOUGH WE WERE IN PIT, BROKE, FOR OVER 6 HRS. I WAS THE ONE WHO INFORMED THEM. CREW SCHEDULING HAS THE CAPABILITY TO PROVIDE THE CREW WITH A DUTY BREAK (IF THE KNOWN DELAY IS TO BE OVER 2 HRS) IN ORDER TO 'INSURE FUTURE LEGALITY.' THAT DUTY BREAK WAS NEVER OFFERED AND WE WERE IN PIT FOR OVER 6 HRS. AGAIN, IS IT MY JOB OUT THERE ON THE LINE TO MONITOR SUCH ISSUES? I CALLED THE COMPANY APPROX 10 MINS PRIOR TO BLOCKOUT AND TOLD THEM TO INVESTIGATE THE SIT. I WAS TOO BUSY AT THAT TIME TRYING TO COMPLETE MY DUTIES IN PREPARATION FOR DEP. IT TOOK APPROX 22-25 MINS FOR THEM TO CONTACT US. WE WERE WELL ON OUR WAY BY THEN. FAR 121.505 STATES THAT THE MAX DUTY LIMIT IS 16 HRS, HOWEVER, IT PROVIDES NO GUIDANCE (THAT I COULD FIND) AS TO IF THAT IS SCHEDULED DUTY TIME OR ACTUAL TIME. IT IMPLIES ACTUAL TIME. IN THAT CASE, WHERE IS THE GUIDANCE COVERING SITS WHERE YOUR FLT IS PLANNED TO MEET DUTY LIMITS BUT DUE TO ATC DELAYS, WX, ETC, YOU EXCEED THOSE LIMITS? THE FCH STATES THAT NO FLT MAY DEPART IF IT WILL EXCEED THE DUTY LIMITS. AGAIN, WHAT HAPPENS IF YOU DON'T PLAN ON EXCEEDING THEM BUT DUE TO UNEXPECTED DELAYS YOU DO EXCEED LIMITS? IT IS BETTER TO ANTICIPATE A DUTY LIMIT PROB THAN TO PUSH THE LIMITS. FAR 121.505 COULD BETTER DEFINE SITS SUCH AS THAT EXPERIENCED ABOVE. CAN YOU BLOCK OUT WITH THE INTENTION OF MEETING THE 16 HR DUTY LIMIT AND ONCE ENRTE, EXCEED 16 HRS DUE TO UNANTICIPATED DELAYS? IN CONCLUSION, THIS SIT PLACED AN UNNECESSARY BURDEN ON THE FLC. SINCE THE 'BIG PICTURE' IS MAINTAINED BY THE COMPANY DISPATCHERS, THEY NEED TO TAKE A COMMANDING ROLE IN DETERMINING WHEN DUTY BREAKS ARE JUSTIFIED.
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.