37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1124330 |
Time | |
Date | 201309 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZDC.ARTCC |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | STAR Aldan1 RDU |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 110 Flight Crew Total 13000 Flight Crew Type 5000 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Descent had been initiated into rdu via routing of the aldan 1 STAR. Altitude changes had been given in steps by ATC. About 2 minutes prior to arrival over sbv VOR the controller hurriedly advised to 'descend via the aldan 1' which meant we were now responsible for all altitude changes. This clearance was not given in time to program the VNAV and resulted in arriving over sbv VOR some 3;000 ft high. Once we caught up we were able to comply with subsequent crossing restrictions. This has become an all too common ATC approach to the 'descend via' stars. Most of the time the clearance is not transmitted in time to allow an orderly programming of the FMS and results in a mad scramble to make initial crossing restrictions if they are made at all. When initial descents are provided by ATC and then the 'descend via' requirement is added; it appears that ATC is dumping altitude responsibilities off on the cockpit crew. Crews can and do make these stars work every day but only when ATC communicates the requirement in a manner that allows enough time for programming and briefing. Short of that; it is a mad rush to catch up and safety of the flight is compromised. My plan is to ask ATC if we can anticipate the 'descend via' clearance as soon as possible and get it programmed ahead of time.
Original NASA ASRS Text
Title: A Corporate crew was issued a descend VIA on the RDU ALDAN 1 STAR after being kept high on the profile and commented that ATC is expecting flight crews to 'catch up' and 'comply' after previous non profile step down descent clearances.
Narrative: Descent had been initiated into RDU via routing of the Aldan 1 STAR. Altitude changes had been given in steps by ATC. About 2 minutes prior to arrival over SBV VOR the Controller hurriedly advised to 'descend via the Aldan 1' which meant we were now responsible for all altitude changes. This clearance was not given in time to program the VNAV and resulted in arriving over SBV VOR some 3;000 FT high. Once we caught up we were able to comply with subsequent crossing restrictions. This has become an all too common ATC approach to the 'descend via' STARS. Most of the time the clearance is not transmitted in time to allow an orderly programming of the FMS and results in a mad scramble to make initial crossing restrictions if they are made at all. When initial descents are provided by ATC and then the 'descend via' requirement is added; it appears that ATC is dumping altitude responsibilities off on the cockpit crew. Crews can and do make these STARs work every day but only when ATC communicates the requirement in a manner that allows enough time for programming and briefing. Short of that; it is a mad rush to catch up and safety of the flight is compromised. My plan is to ask ATC if we can anticipate the 'descend via' clearance as soon as possible and get it programmed ahead of time.
Data retrieved from NASA's ASRS site as of July 2013 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.