37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1246749 |
Time | |
Date | 201503 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ASE.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Citation X (C750) |
Operating Under FAR Part | Part 135 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance |
Narrative:
During our initial descent into ase we were given several speed changes and delay vectors. Our first delay was about 15 miles northeast of the field and was vector that lead to a left 360 degree turn to a heading of 320 at 16;000 ft. This was followed by a right turn to a heading of 360 and a speed change to 210 knots; then 170 knots; then 10 knots less and then a question of what's your speed. We said 170 and slowing to 160. Then we got a heading of 270 degrees that ended in a vector through the final approach course. At this time we were cleared direct jargu which is the first fix inside dbl (red table VOR) when we received the clearance we were 6 NM outside of jargu. The approach controller asked us if we have the field insight; we replied yes and was instructed 'cleared direct the field for the visual approach' at this time the altitude selector was already set to 13;400 feet. At that time we configured the airplane for landing and left 16;000 feet for 13;400 ft. Thinking we heard 'cleared for the visual approach' as we descended through 15;300 feet the controller queried our altitude and we read back 15;200 ft. The approach controller advised us that we were supposed to maintain 16;000 feet but that we were now in his airspace and were now cleared for the visual approach. The rest of the approach continued without incident. After clearing the runway; ground control asked us to call the tower cab regarding a pilot deviation.I believe we maintained situational awareness throughout the entire approach into ase. ATC was operating at maximum capacity at the time of flight. Several delay vectors and assigned speeds were given to us to accommodate their high traffic volume. The approach controller left us high inside red table VOR and it was getting close to not being able to clear us for the approach. Everything was pointing to a visual approach as it was the controller's last option. The phraseology of 'cleared direct to the field for approach' and the need to make our upcoming crossing altitude lead to hear/ interpret the we were cleared for the visual.it is our responsibility as a crew to verify any instructions issued by ATC. This situation has allowed me to re-evaluate my CRM and challenge ATC if anything seems out of the ordinary in regards to instructions.
Original NASA ASRS Text
Title: CE-750 flight crew experiences many heading assignments and speed changes arrival into ASE. Eventually; with the field in sight; the crew is 'cleared direct the field for the visual approach'. The words 'cleared for the approach' were not issued but the crew assumed they were and begins descent. The error is pointed out and the visual approach clearance is issued.
Narrative: During our initial descent into ASE we were given several speed changes and delay vectors. Our first delay was about 15 miles northeast of the field and was vector that lead to a left 360 degree turn to a heading of 320 at 16;000 ft. This was followed by a right turn to a heading of 360 and a speed change to 210 knots; then 170 knots; then 10 knots less and then a question of what's your speed. We said 170 and slowing to 160. Then we got a heading of 270 degrees that ended in a vector through the final approach course. At this time we were cleared direct JARGU which is the first fix inside DBL (Red Table VOR) when we received the clearance we were 6 NM outside of JARGU. The approach controller asked us if we have the field insight; we replied yes and was instructed 'cleared direct the field for the visual approach' at this time the altitude selector was already set to 13;400 feet. At that time we configured the airplane for landing and left 16;000 feet for 13;400 ft. Thinking we heard 'cleared for the visual approach' as we descended through 15;300 feet the controller queried our altitude and we read back 15;200 ft. The approach controller advised us that we were supposed to maintain 16;000 feet but that we were now in his airspace and were now cleared for the visual approach. The rest of the approach continued without incident. After clearing the runway; ground control asked us to call the tower cab regarding a pilot deviation.I believe we maintained situational awareness throughout the entire approach into ASE. ATC was operating at maximum capacity at the time of flight. Several delay vectors and assigned speeds were given to us to accommodate their high traffic volume. The approach controller left us high inside red table VOR and it was getting close to not being able to clear us for the approach. Everything was pointing to a visual approach as it was the controller's last option. The phraseology of 'cleared direct to the field for approach' and the need to make our upcoming crossing altitude lead to hear/ interpret the we were cleared for the visual.It is our responsibility as a crew to verify any instructions issued by ATC. This situation has allowed me to re-evaluate my CRM and challenge ATC if anything seems out of the ordinary in regards to instructions.
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.