37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1748726 |
Time | |
Date | 202006 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR ZZZZZX |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Undershoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Narrative:
I was the pm on aircraft X from ZZZ1 to ZZZ. Our arrival was as planned per the pre departure clearance. As we approached zzzzz (the transition fix); the ATC controller said; 'aircraft X; cleared the zzzzzx arrival for the zzzzzy visual runway xx'. I acknowledged ATC and then asked the ca if he heard 'descend via'? The ca and I agreed that we did not hear 'descend via' and therefore stayed at FL310 until I could query the controller. We had 27.6 NM to the next altitude constraint (approximately four minutes) and the radios were busy with constant chatter. I was finally able to query the controller approximately 7 NM prior to ZZZZZ2 with an altitude constraint of FL280-240. ATC said that he expected us to have descended; then cleared us direct to ZZZZZ3 to resume the arrival with published altitudes and speeds. The ca started to descend; there were no further questions or issues with the clearance; and we had an uneventful arrival/approach/landing. The controller was not mad; nor did he ask us to call him after we landed. Lastly; there were no traffic concerns; nor was safety an issue.both the ca and I had not flown in two or more months so we were being extra vigilant with a heightened awareness. A definite causal factor was the busy radio which made it hard to communicate with ATC in a timely fashion before losing a 3:1 descent profile and causing a more aggressive descent to meet the published altitudes on the zzzzzx RNAV arrival. More importantly; the #1 causal factor was the lack of proper vertical clearance verbiage by ATC. Both the ca and I expected to hear; 'descend via' but that was not stated. There was no clearance to descend out of FL310; only 'cleared the zzzzzx arrival'. After reviewing the fom section XXXX; we executed correctly.fom section XXXX standard terminal arrival route (STAR) clearancessource: aim & information 12003 an ATC arrival clearance using the phraseology 'cleared arrival
Original NASA ASRS Text
Title: Air carrier Captain reported being unsure if they were supposed to descend on the approach clearance received from ATC resulting in an altitude deviation.
Narrative: I was the PM on Aircraft X from ZZZ1 to ZZZ. Our arrival was as planned per the PDC. As we approached ZZZZZ (the transition fix); the ATC controller said; 'Aircraft X; cleared the ZZZZZX arrival for the ZZZZZY VISUAL RWY XX'. I acknowledged ATC and then asked the CA if he heard 'descend via'? The CA and I agreed that we did not hear 'descend via' and therefore stayed at FL310 until I could query the Controller. We had 27.6 NM to the next altitude constraint (approximately four minutes) and the radios were busy with constant chatter. I was finally able to query the Controller approximately 7 NM prior to ZZZZZ2 with an altitude constraint of FL280-240. ATC said that he expected us to have descended; then cleared us direct to ZZZZZ3 to resume the arrival with published altitudes and speeds. The CA started to descend; there were no further questions or issues with the clearance; and we had an uneventful arrival/approach/landing. The Controller was not mad; nor did he ask us to call him after we landed. Lastly; there were no traffic concerns; nor was safety an issue.Both the CA and I had not flown in two or more months so we were being extra vigilant with a heightened awareness. A definite causal factor was the busy radio which made it hard to communicate with ATC in a timely fashion before losing a 3:1 descent profile and causing a more aggressive descent to meet the published altitudes on the ZZZZZX RNAV Arrival. More importantly; the #1 causal factor was the lack of proper vertical clearance verbiage by ATC. Both the CA and I expected to hear; 'descend via' but that was not stated. There was no clearance to descend out of FL310; only 'cleared the ZZZZZX ARRIVAL'. After reviewing the FOM Section XXXX; we executed correctly.FOM Section XXXX Standard Terminal Arrival Route (STAR) ClearancesSource: AIM & INFO 12003 An ATC arrival clearance using the phraseology 'Cleared arrival
Data retrieved from NASA's ASRS site 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.