Narrative:

We were being given delayed vectors at 3;000 ft to set up for the VOR 16 approach into daytona beach international. Approach control assigned us a heading and instructed us to intercept the final approach course. We were 1 minute 30 seconds away from the final approach fix and still at 3;000 ft which is 1;400 ft higher than published and higher than where we usually are when the controller cleared us for the approach. Just prior to that; my student and I were discussing the height issue and how procedure turns are used to address that kind of issue. When the controller gave us the approach clearance; I asked 'are we cleared for the straight in?' for clarification as to whether or not the procedure turn should be flown. To which she replied; 'no; cleared for the VOR 16; circle to land 7L.' I read that back and the student did the procedure turn upon crossing the initial/final approach fix. Halfway through the turn; the controller came back over the radio asking why we were doing what we were doing. I replied with; 'you told us not cleared for the straight in.' to which she replied 'no; you're not cleared for straight in 16; you're cleared for the circle. I thought you were asking if you were cleared for the straight in landing on 16' we were then instructed to intercept the final approach course again and cleared for the approach with no further issues.there was a misunderstanding between pilot and controller as to what was meant by 'are we cleared for the straight-in?' in the instrument procedures handbook [FAA-H-8261-1A section 5-39] it reads; '...ATC may specify in the approach clearance; cleared straight-in (type) approach to ensure that the pilot understands that the procedure turn or hold-in-lieu-of-pt is not to be flown. If the pilot is uncertain whether ATC intends for a procedure turn or a straight-in approach to be flown; the pilot shall immediately request clarification.'

Google
 

Original NASA ASRS Text

Title: Confusion reigned between Approach Control and the instructor/student pilots of a C172 on vectors for the VOR Runway 16 IAP at DAB regarding the expectation to perform the published procedure turn.

Narrative: We were being given delayed vectors at 3;000 FT to set up for the VOR 16 approach into Daytona Beach International. Approach control assigned us a heading and instructed us to intercept the final approach course. We were 1 minute 30 seconds away from the Final Approach Fix and still at 3;000 FT which is 1;400 FT higher than published and higher than where we usually are when the Controller cleared us for the approach. Just prior to that; my student and I were discussing the height issue and how procedure turns are used to address that kind of issue. When the Controller gave us the approach clearance; I asked 'are we cleared for the straight in?' for clarification as to whether or not the procedure turn should be flown. To which she replied; 'No; Cleared for the VOR 16; circle to land 7L.' I read that back and the student did the procedure turn upon crossing the initial/final approach fix. Halfway through the turn; the Controller came back over the radio asking why we were doing what we were doing. I replied with; 'You told us not cleared for the straight in.' To which she replied 'No; you're not cleared for straight in 16; you're cleared for the circle. I thought you were asking if you were cleared for the straight in landing on 16' We were then instructed to intercept the final approach course again and cleared for the approach with no further issues.There was a misunderstanding between pilot and Controller as to what was meant by 'Are we cleared for the straight-in?' In the Instrument Procedures Handbook [FAA-H-8261-1A Section 5-39] it reads; '...ATC may specify in the approach clearance; cleared straight-in (type) approach to ensure that the pilot understands that the procedure turn or hold-in-lieu-of-PT is not to be flown. If the pilot is uncertain whether ATC intends for a procedure turn or a straight-in approach to be flown; the pilot shall immediately request clarification.'

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.