 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Descent not started and crossing restr not met by an air carrier crew involved in planning the next flight for their next departure.
| Attributes | |
| ACN | 530906 |
| Time | |
| Date | 200111 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | navaid : slt.vortac |
| State Reference | PA |
| Altitude | msl bound lower : 29000 msl bound upper : 35000 |
| Aircraft 1 | |
| Controlling Facilities | artcc : zob.artcc artcc : zfw.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other vortac |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 190 flight time total : 15300 flight time type : 2875 |
| ASRS Report | 530906 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time type : 594 |
| ASRS Report | 531195 |
| Events | |
| Anomaly | altitude deviation : crossing restriction not met non adherence : clearance non adherence : company policies other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | other |
| Supplementary | |
| Problem Areas | Company Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
En route to ewr at FL350, ZOB issued us a clearance to cross slt at FL330. Then immediately reissued a clearance to cross slt at FL290. Just prior to issuing clearance, we called for flight plan data through ACARS. We set altitude for FL290, pointed at it and even said where I would start down as I always figure a descent point. Started to flight plan next leg and we were approaching slt at FL350. ATC then issued a clearance for us to descend to FL330 with no mention of the crossing we missed. Descended immediately and asked if he wanted us at FL290 or FL330 and he said FL330. We got distracted by trying to flight plan while on arrival. In the future, I will keep aircraft in VNAV, but VNAV sometimes crosses us high and I didn't want to do that. Also, ACARS prints flight plan and data so slow out that we are constantly looking for more information about next flight. It is a distraction as sometimes data comes out just as we are approaching our top of descent point.
Original NASA ASRS Text
Title: DSCNT NOT STARTED AND XING RESTR NOT MET BY AN ACR CREW INVOLVED IN PLANNING THE NEXT FLT FOR THEIR NEXT DEP.
Narrative: ENRTE TO EWR AT FL350, ZOB ISSUED US A CLRNC TO CROSS SLT AT FL330. THEN IMMEDIATELY REISSUED A CLRNC TO CROSS SLT AT FL290. JUST PRIOR TO ISSUING CLRNC, WE CALLED FOR FLT PLAN DATA THROUGH ACARS. WE SET ALT FOR FL290, POINTED AT IT AND EVEN SAID WHERE I WOULD START DOWN AS I ALWAYS FIGURE A DSCNT POINT. STARTED TO FLT PLAN NEXT LEG AND WE WERE APCHING SLT AT FL350. ATC THEN ISSUED A CLRNC FOR US TO DSND TO FL330 WITH NO MENTION OF THE XING WE MISSED. DSNDED IMMEDIATELY AND ASKED IF HE WANTED US AT FL290 OR FL330 AND HE SAID FL330. WE GOT DISTRACTED BY TRYING TO FLT PLAN WHILE ON ARR. IN THE FUTURE, I WILL KEEP ACFT IN VNAV, BUT VNAV SOMETIMES CROSSES US HIGH AND I DIDN'T WANT TO DO THAT. ALSO, ACARS PRINTS FLT PLAN AND DATA SO SLOW OUT THAT WE ARE CONSTANTLY LOOKING FOR MORE INFO ABOUT NEXT FLT. IT IS A DISTR AS SOMETIMES DATA COMES OUT JUST AS WE ARE APCHING OUR TOP OF DSCNT POINT.
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.