37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1452374 |
Time | |
Date | 201705 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | OAK.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 35 Flight Crew Total 450 Flight Crew Type 310 |
Person 2 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
I was instructed by ATC to maintain 3400 ft on vectors to final ILS 28R oak. I then intercepted localizer and was cleared for the approach. I continued my intercept; as localizer CDI was active but not yet fully intercepted. I turned to an estimated heading of 240. Upon noticing that I had an excess altitude of nearly 500 ft; I needed to increase my descent. I notified ATC of my intention to perform a left hand 360-degree turn and re-intercept localizer. I was in VMC; and had simply needed a reminder that upon receiving my IFR clearance; the responsibility of terrain and traffic avoidance became shared by ATC and myself. Approximately 90 degrees into the turn and after a response from ATC; I corrected the action and turned back on the proper heading by which time a possible pilot deviation had been noted. Cause for the excess altitude was a pilot lack of situational awareness. I expected to intercept localizer at grove; but instead was approaching urzaf. Factors affecting the quality of my performance under IFR was a direct result of unclear distinction as to when I fell under IFR regulations. In practice approaches in VFR conditions; when ATC was not responsible for aircraft separation; there was more flexibility in procedures. I called norcal approach when I completed my flight; and have been actively cooperating with any and all requests thereafter.
Original NASA ASRS Text
Title: C172 pilot and TRACON Controller reported confusion on the part of the pilot about following ATC instructions under an IFR clearance.
Narrative: I was instructed by ATC to maintain 3400 ft on vectors to final ILS 28R OAK. I then intercepted localizer and was cleared for the approach. I continued my intercept; as localizer CDI was active but not yet fully intercepted. I turned to an estimated heading of 240. Upon noticing that I had an excess altitude of nearly 500 ft; I needed to increase my descent. I notified ATC of my intention to perform a left hand 360-degree turn and re-intercept localizer. I was in VMC; and had simply needed a reminder that upon receiving my IFR clearance; the responsibility of terrain and traffic avoidance became shared by ATC and myself. Approximately 90 degrees into the turn and after a response from ATC; I corrected the action and turned back on the proper heading by which time a possible pilot deviation had been noted. Cause for the excess altitude was a pilot lack of situational awareness. I expected to intercept localizer at GROVE; but instead was approaching URZAF. Factors affecting the quality of my performance under IFR was a direct result of unclear distinction as to when I fell under IFR regulations. In practice approaches in VFR conditions; when ATC was not responsible for aircraft separation; there was more flexibility in procedures. I called Norcal Approach when I completed my flight; and have been actively cooperating with any and all requests thereafter.
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.