Narrative:

We were on our last leg of the day; flying into avl. It was leg 5 for me on 11th hour of duty; leg 7 for the captain almost 14 hours of duty; night; raining; non-towered; mountainous terrain airport; with an apparently confusing approach. Not a good setup. We were expecting the ILS 34; and I briefed and set up the approach. We were filed direct sug direct avl. Around sug; we were told to descend to 7;000 ft. We were told maintain 7;000; then given direct broad river (bra) and cleared for the ILS 34 approach. In looking at the approach plate; the minimum altitude between sug and bra is 5;500 ft and the minimum altitude at bra is 4;400 ft. No where on the plate does it say you must cross bra at a higher altitude and use the procedure turn to descend. On the plate for ILS 16 in avl it does depict this and is clear about it. So we began our descent so that we could cross bra at 4;400 and continue on the ILS 34. ATC informed us we had busted altitude and to climb back to 7;000 until crossing bra. At this time; we were not expecting to do a procedure turn; and the FMS was setup to continue the approach from bra; so at 7;000; we turned inbound; knowing that there was no way we could land with a stabilized approach from this altitude. The captain informed ATC; and she told us that we were expected to perform the procedure turn on the approach. We made a left 180 and then she vectored us out back towards sug to send us in again. This second time; we made the procedure turn and landed uneventfully.to the best of my memory; I do not recall the controller clearing us for the 'full' approach. I think that would have made a difference in how we handled the situation. There are two prongs to that. If she did say cleared for the full approach; neither of us heard or acknowledged it. I think that is attributable to fatigue issues having to do with such a late flight; after a long day; with many factors complicating the flight. Also; she should have challenged the captain's read back when he did not acknowledge the full approach and clarified that we needed to perform the procedure turn. If she did not say cleared for the 'full' approach but we still should have done it; then we need to review phraseology and what the controllers' commands do mean. It is possible that operating in the usual towered environment; we become so used to 'cleared for the approach' meaning straight in when you get the localizer; when technically something else may be expected. In conclusion; I think we need to be highly vigilant to pinpoint any operations that may be out of the ordinary and be prepared to check and double check what we are doing. I think being aware of our physical limits when approaching fatigue and how they will affect our performance is also very important. Lastly; we need to be sure we understand what ATC expects of us; and clarify it with them whenever necessary.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier flight crew reports confusion over the requirement to fly the holding pattern procedure turn from SUG to the ILS 34 approach at AVL.

Narrative: We were on our last leg of the day; flying into AVL. It was leg 5 for me on 11th hour of duty; leg 7 for the Captain almost 14 hours of duty; night; raining; non-towered; mountainous terrain airport; with an apparently confusing approach. Not a good setup. We were expecting the ILS 34; and I briefed and set up the approach. We were filed direct SUG direct AVL. Around SUG; we were told to descend to 7;000 FT. We were told maintain 7;000; then given direct Broad River (BRA) and cleared for the ILS 34 approach. In looking at the approach plate; the minimum altitude between SUG and BRA is 5;500 FT and the minimum altitude at BRA is 4;400 FT. No where on the plate does it say you must cross BRA at a higher altitude and use the procedure turn to descend. On the plate for ILS 16 in AVL it does depict this and is clear about it. So we began our descent so that we could cross BRA at 4;400 and continue on the ILS 34. ATC informed us we had busted altitude and to climb back to 7;000 until crossing BRA. At this time; we were not expecting to do a procedure turn; and the FMS was setup to continue the approach from BRA; so at 7;000; we turned inbound; knowing that there was no way we could land with a stabilized approach from this altitude. The Captain informed ATC; and she told us that we were expected to perform the procedure turn on the approach. We made a left 180 and then she vectored us out back towards SUG to send us in again. This second time; we made the procedure turn and landed uneventfully.To the best of my memory; I do not recall the Controller clearing us for the 'full' approach. I think that would have made a difference in how we handled the situation. There are two prongs to that. If she did say cleared for the FULL approach; neither of us heard or acknowledged it. I think that is attributable to fatigue issues having to do with such a late flight; after a long day; with many factors complicating the flight. Also; she should have challenged the Captain's read back when he did not acknowledge the full approach and clarified that we needed to perform the procedure turn. If she did not say cleared for the 'full' approach but we still should have done it; then we need to review phraseology and what the Controllers' commands do mean. It is possible that operating in the usual towered environment; we become so used to 'cleared for the approach' meaning straight in when you get the localizer; when technically something else may be expected. In conclusion; I think we need to be highly vigilant to pinpoint any operations that may be out of the ordinary and be prepared to check and double check what we are doing. I think being aware of our physical limits when approaching fatigue and how they will affect our performance is also very important. Lastly; we need to be sure we understand what ATC expects of us; and clarify it with them whenever necessary.

Data retrieved from NASA's ASRS site as of April 2012 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.