 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier freighter flight crew are high at a crossing point when a ZNY controller gives the restr too late and does not coordinate with the next controller. Large transport.
| Attributes | |
| ACN | 350664 |
| Time | |
| Date | 199610 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : lrp |
| State Reference | PA |
| Altitude | msl bound lower : 25000 msl bound upper : 25500 |
| Environment | |
| Flight Conditions | IMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | descent other |
| Route In Use | arrival other arrival star : star |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 50 flight time total : 25000 flight time type : 2650 |
| ASRS Report | 350664 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 40 flight time total : 3000 flight time type : 40 |
| ASRS Report | 350814 |
| Events | |
| Anomaly | altitude deviation : crossing restriction not met |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | none taken : unable |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
En route to phl at 33000 ft on the bucks 4 arrival ZNY issued us a clearance to cross 45 mi west of lancaster VOR at FL250 in less than 10 mi to the crossing fix. Maximum descent was accomplished and center was advised that we most likely would not make FL250 by 45 mi west of lrp and the controller replied, report out of FL260 and that he would have to point us out (not sure of what this meant). Due to congestion on the frequency we were unable to call out of FL260, but was able to cross 45 mi west of lrp at FL255. After having flown this same route at the same time every day this week, I can report that this sector controller's workload is very high. It appears to me that some of this workload could be reduced if more crossing altitudes could be profiled on the bucks 4 arrival rather than have the controller assign a different crossing fix for every aircraft on the arrival.
Original NASA ASRS Text
Title: AN ACR FREIGHTER FLC ARE HIGH AT A XING POINT WHEN A ZNY CTLR GIVES THE RESTR TOO LATE AND DOES NOT COORDINATE WITH THE NEXT CTLR. LGT.
Narrative: ENRTE TO PHL AT 33000 FT ON THE BUCKS 4 ARR ZNY ISSUED US A CLRNC TO CROSS 45 MI W OF LANCASTER VOR AT FL250 IN LESS THAN 10 MI TO THE XING FIX. MAX DSCNT WAS ACCOMPLISHED AND CTR WAS ADVISED THAT WE MOST LIKELY WOULD NOT MAKE FL250 BY 45 MI W OF LRP AND THE CTLR REPLIED, RPT OUT OF FL260 AND THAT HE WOULD HAVE TO POINT US OUT (NOT SURE OF WHAT THIS MEANT). DUE TO CONGESTION ON THE FREQ WE WERE UNABLE TO CALL OUT OF FL260, BUT WAS ABLE TO CROSS 45 MI W OF LRP AT FL255. AFTER HAVING FLOWN THIS SAME RTE AT THE SAME TIME EVERY DAY THIS WK, I CAN RPT THAT THIS SECTOR CTLR'S WORKLOAD IS VERY HIGH. IT APPEARS TO ME THAT SOME OF THIS WORKLOAD COULD BE REDUCED IF MORE XING ALTS COULD BE PROFILED ON THE BUCKS 4 ARR RATHER THAN HAVE THE CTLR ASSIGN A DIFFERENT XING FIX FOR EVERY ACFT ON THE ARR.
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.