37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1488882 |
Time | |
Date | 201710 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | EWN.Airport |
State Reference | NC |
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 |
Flight Plan | VFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 2 Flight Crew Total 1100 Flight Crew Type 1000 |
Person 2 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 310 Flight Crew Type 70 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was conducting practice approaches and was in contact with approach. I was the pilot-in-command; with a CFI from a local flight school acting as safety pilot. We had requested and were given the ILS runway 4 approach; had been cleared onto the final approach course; and had instructions to expect a circle-to-land to runway 22 (this was the active runway) although my intention was not to land but to proceed to another practice approach. Upon intercepting the final approach course and proceeding inbound; I had some expectation to be turned over to tower frequency; but I don't recall this occurring until nearing the airport; when cherry point asked if I had contacted the tower; at which I point I did so and was informed of a potential airspace violation and to call the tower manager at a specified number. At that point I returned to land and called the number that was provided and spoke to the controller. I was informed the manager was not present but to speak with him the following morning. I have been informed this was considered a violation as it did not occur while flying on an instrument flight plan; and it was therefore my responsibility to contact the tower for clearance.
Original NASA ASRS Text
Title: C172 pilots reported they did not recall an instruction to contact the Tower until already having entered the Tower's airspace.
Narrative: I was conducting practice approaches and was in contact with Approach. I was the pilot-in-command; with a CFI from a local flight school acting as safety pilot. We had requested and were given the ILS runway 4 approach; had been cleared onto the final approach course; and had instructions to expect a circle-to-land to runway 22 (this was the active runway) although my intention was not to land but to proceed to another practice approach. Upon intercepting the final approach course and proceeding inbound; I had some expectation to be turned over to tower frequency; but I don't recall this occurring until nearing the airport; when Cherry Point asked if I had contacted the tower; at which I point I did so and was informed of a potential airspace violation and to call the tower manager at a specified number. At that point I returned to land and called the number that was provided and spoke to the controller. I was informed the manager was not present but to speak with him the following morning. I have been informed this was considered a violation as it did not occur while flying on an instrument flight plan; and it was therefore my responsibility to contact the tower for clearance.
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.