 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
New first officer to air carrier of a DC9 believes that he exceeded flight time duty limitations by going slightly over 30 flight hours in a 7 consecutive day period. However, the far permits 32 hours. Therefore, it may have been an employee rule to which he was referring. He also believed that he did not complete 24 of consecutive rest in 7 days. However, due to the flight delay it could be completed after his deadhead flight.
| Attributes | |
| ACN | 402460 |
| Time | |
| Date | 199805 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : msp |
| State Reference | MN |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Dusk |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | DC-9 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : preflight |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 120 flight time type : 120 |
| ASRS Report | 402460 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | non adherence other other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
I am a new hire reserve pilot. We do not get trip pairings and time cycles with our paperwork when we are sent on a trip. However, the scheduler must tell you if you are approaching violations. In addition to this, when assigned these trips, I asked if I had a 30 in 7 problem and was told no. What the scheduler did was force the computer to accept the assignment and lie to me about it. Unknown to me I busted the 30 in 7 rule by a small margin. When on the way home from this assignment my deadhead flight was delayed about 4 1/2 hours, putting me into the next day. So the computer also shows no 24 hour in 7, but it was a deadhead and I did need to go home.
Original NASA ASRS Text
Title: NEW FO TO ACR OF A DC9 BELIEVES THAT HE EXCEEDED FLT TIME DUTY LIMITATIONS BY GOING SLIGHTLY OVER 30 FLT HRS IN A 7 CONSECUTIVE DAY PERIOD. HOWEVER, THE FAR PERMITS 32 HRS. THEREFORE, IT MAY HAVE BEEN AN EMPLOYEE RULE TO WHICH HE WAS REFERRING. HE ALSO BELIEVED THAT HE DID NOT COMPLETE 24 OF CONSECUTIVE REST IN 7 DAYS. HOWEVER, DUE TO THE FLT DELAY IT COULD BE COMPLETED AFTER HIS DEADHEAD FLT.
Narrative: I AM A NEW HIRE RESERVE PLT. WE DO NOT GET TRIP PAIRINGS AND TIME CYCLES WITH OUR PAPERWORK WHEN WE ARE SENT ON A TRIP. HOWEVER, THE SCHEDULER MUST TELL YOU IF YOU ARE APCHING VIOLATIONS. IN ADDITION TO THIS, WHEN ASSIGNED THESE TRIPS, I ASKED IF I HAD A 30 IN 7 PROB AND WAS TOLD NO. WHAT THE SCHEDULER DID WAS FORCE THE COMPUTER TO ACCEPT THE ASSIGNMENT AND LIE TO ME ABOUT IT. UNKNOWN TO ME I BUSTED THE 30 IN 7 RULE BY A SMALL MARGIN. WHEN ON THE WAY HOME FROM THIS ASSIGNMENT MY DEADHEAD FLT WAS DELAYED ABOUT 4 1/2 HRS, PUTTING ME INTO THE NEXT DAY. SO THE COMPUTER ALSO SHOWS NO 24 HR IN 7, BUT IT WAS A DEADHEAD AND I DID NEED TO GO HOME.
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.