37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 519079 |
Time | |
Date | 200107 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : vuz.vortac |
State Reference | AL |
Altitude | msl single value : 11000 |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zme.artcc |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | cruise : enroute altitude change |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : instrument pilot : multi engine pilot : commercial |
Experience | flight time last 90 days : 120 flight time total : 1500 flight time type : 250 |
ASRS Report | 519079 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | altitude deviation : crossing restriction not met non adherence : clearance |
Independent Detector | atc equipment other atc equipment : radar other controllera other flight crewa |
Resolutory Action | controller : issued new clearance none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
ATC issued crossing restr 38 NM northwest of vulcan VOR, cross at and maintain 11000 ft. As PNF, I communicated with ATC and performed items on the descent checklist. The captain was performing the duties of PF. Once the descent was initiated, it became apparent to me that the crossing restr could not be met. I continued to perform descent checklist items with the assumption that the captain would increase the descent rate. I communicated with passenger and flight attendants on PA. The captain communicated with ATC while I was speaking on the PA. When I was done speaking on the PA, I realized the descent rate still had not been increased enough. I asked the captain again if he knew where the crossing restr was. At that point, ATC asked if we could meet the restr. The captain said we still could. However, we did not meet the restr. We missed it by approximately 2 NM. ATC then issued a vector for traffic. The controller was very unhappy and stressed the importance of meeting crossing restrs.
Original NASA ASRS Text
Title: ACR PLT FAILS TO MAKE A REQUIRED XING RESTR RESULTING IN A VECTOR BY ATC FOR SEPARATION.
Narrative: ATC ISSUED XING RESTR 38 NM NW OF VULCAN VOR, CROSS AT AND MAINTAIN 11000 FT. AS PNF, I COMMUNICATED WITH ATC AND PERFORMED ITEMS ON THE DSCNT CHKLIST. THE CAPT WAS PERFORMING THE DUTIES OF PF. ONCE THE DSCNT WAS INITIATED, IT BECAME APPARENT TO ME THAT THE XING RESTR COULD NOT BE MET. I CONTINUED TO PERFORM DSCNT CHKLIST ITEMS WITH THE ASSUMPTION THAT THE CAPT WOULD INCREASE THE DSCNT RATE. I COMMUNICATED WITH PAX AND FLT ATTENDANTS ON PA. THE CAPT COMMUNICATED WITH ATC WHILE I WAS SPEAKING ON THE PA. WHEN I WAS DONE SPEAKING ON THE PA, I REALIZED THE DSCNT RATE STILL HAD NOT BEEN INCREASED ENOUGH. I ASKED THE CAPT AGAIN IF HE KNEW WHERE THE XING RESTR WAS. AT THAT POINT, ATC ASKED IF WE COULD MEET THE RESTR. THE CAPT SAID WE STILL COULD. HOWEVER, WE DID NOT MEET THE RESTR. WE MISSED IT BY APPROX 2 NM. ATC THEN ISSUED A VECTOR FOR TFC. THE CTLR WAS VERY UNHAPPY AND STRESSED THE IMPORTANCE OF MEETING XING RESTRS.
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.