37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 423510 |
Time | |
Date | 199812 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mem |
State Reference | TN |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Flight Phase | other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : instrument pilot : flight engineer |
Experience | flight time last 90 days : 100 flight time total : 3600 flight time type : 100 |
ASRS Report | 423510 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | non adherence : far non adherence other other anomaly other |
Independent Detector | other flight crewa other other : unspecified |
Resolutory Action | none taken : detected after the fact other |
Consequence | Other |
Supplementary | |
Air Traffic Incident | other |
Narrative:
2 flts were operated by me for air carrier xyz while I was illegal to fly. I began a 4 leg trip sequence on dec/xa/98 that terminated at approximately XA09Z at mem. Because of an in-flight divert, my captain suggested I contact my crew scheduler for a possible 8 in 24 problem (8 block hours in a 24 hour period). At XA38Z, a scheduler confirmed my ineligibility for a subsequent trip and I was advised that I was 'released for 10 hours.' at approximately XD00Z, crew scheduling called me in from home for another trip. Because of operational uncertainties, I did not begin my next trip until approximately XA00Z, dec/xb/98. Shortly before blocking out at cos for the third, final, and return leg to mem, goc contacted me and grounded our flight. The 'system' had eventually uncovered my illegality and flight management terminated our flight. Causes: personal ignorance of crew rest requirements following an 8 in 24 situation. Failure of schedulers to provide 16 hour or twice actual block instead of the 'standard' 10 hour crew rest period and/or failure of computer or failure to provide timely input to computer crew duty oversight program. (These are logical inferences at present -- actual sequence of controller/scheduler actions are not yet known to me.) influencing factors: 1) peak period is hectic at air carrier and we were under an 'operation emergency' status because of an ice storm. Some normal crew duty constraints are relaxed (ie, 16 hour crew duty vice normal 12 hour crew duty). Led to my personal confusion and perhaps the crew scheduler's. 2) the incredible pace of operations and associated fatigue of operating to far limits may have lowered the vigilance for regulation conflicts on both my part and that of schedulers.
Original NASA ASRS Text
Title: FLC UNFAMILIARITY WITH FLT TIME LIMITATIONS IN FARS. FLC MEMBER ERRONEOUSLY RELIES ON CREW SCHEDULING TO MAINTAIN HIS LEGALITY.
Narrative: 2 FLTS WERE OPERATED BY ME FOR ACR XYZ WHILE I WAS ILLEGAL TO FLY. I BEGAN A 4 LEG TRIP SEQUENCE ON DEC/XA/98 THAT TERMINATED AT APPROX XA09Z AT MEM. BECAUSE OF AN INFLT DIVERT, MY CAPT SUGGESTED I CONTACT MY CREW SCHEDULER FOR A POSSIBLE 8 IN 24 PROB (8 BLOCK HRS IN A 24 HR PERIOD). AT XA38Z, A SCHEDULER CONFIRMED MY INELIGIBILITY FOR A SUBSEQUENT TRIP AND I WAS ADVISED THAT I WAS 'RELEASED FOR 10 HRS.' AT APPROX XD00Z, CREW SCHEDULING CALLED ME IN FROM HOME FOR ANOTHER TRIP. BECAUSE OF OPERATIONAL UNCERTAINTIES, I DID NOT BEGIN MY NEXT TRIP UNTIL APPROX XA00Z, DEC/XB/98. SHORTLY BEFORE BLOCKING OUT AT COS FOR THE THIRD, FINAL, AND RETURN LEG TO MEM, GOC CONTACTED ME AND GNDED OUR FLT. THE 'SYS' HAD EVENTUALLY UNCOVERED MY ILLEGALITY AND FLT MGMNT TERMINATED OUR FLT. CAUSES: PERSONAL IGNORANCE OF CREW REST REQUIREMENTS FOLLOWING AN 8 IN 24 SIT. FAILURE OF SCHEDULERS TO PROVIDE 16 HR OR TWICE ACTUAL BLOCK INSTEAD OF THE 'STANDARD' 10 HR CREW REST PERIOD AND/OR FAILURE OF COMPUTER OR FAILURE TO PROVIDE TIMELY INPUT TO COMPUTER CREW DUTY OVERSIGHT PROGRAM. (THESE ARE LOGICAL INFERENCES AT PRESENT -- ACTUAL SEQUENCE OF CTLR/SCHEDULER ACTIONS ARE NOT YET KNOWN TO ME.) INFLUENCING FACTORS: 1) PEAK PERIOD IS HECTIC AT ACR AND WE WERE UNDER AN 'OP EMER' STATUS BECAUSE OF AN ICE STORM. SOME NORMAL CREW DUTY CONSTRAINTS ARE RELAXED (IE, 16 HR CREW DUTY VICE NORMAL 12 HR CREW DUTY). LED TO MY PERSONAL CONFUSION AND PERHAPS THE CREW SCHEDULER'S. 2) THE INCREDIBLE PACE OF OPS AND ASSOCIATED FATIGUE OF OPERATING TO FAR LIMITS MAY HAVE LOWERED THE VIGILANCE FOR REG CONFLICTS ON BOTH MY PART AND THAT OF SCHEDULERS.
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.