37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1246858 |
Time | |
Date | 201503 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | HNZ.Airport |
State Reference | NC |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Instructor |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 120 Flight Crew Total 350 Flight Crew Type 250 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Around XA00 I was flying to hnz with my IFR student. We filed a flight plan to hnz then back to ZZZ for a 2 hour flight. We were with raleigh approach receiving vectors for the RNAV GPS for runway 24 at hnz. The controller advised me to proceed direct to a point which I could not locate. I responded to her that I cannot go direct because I cannot find this fix. She just kept telling me to go direct to this imaginary fix; so I just went direct to the IAF for the approach. She said nothing of it so I assumed the point I went to was correct. After the RNAV 24 approach we wanted vectors to shoot the RNAV 6 back in. Instead of going to the IAF and doing a course reversal the controller advised us to go outbound to tucov. Tucov does not exist. We just went outbound until we crossed virginia and I took controls and turned around inbound; I heard nothing from the controller and he cleared me in for the approach. Why would a controller have me fly outbound when I am on the course to do a course reversal is what I was wondering about. After the approach we headed back to ZZZ. I spoke to my boss and we called the raleigh approach on the telephone. Turns out that the controllers had expired charts; hence the reason we had this confusion.
Original NASA ASRS Text
Title: Pilot is told to fly to a fix that is not on his route and flies towards the IAF. On a second approach the controller tells the pilot to go to another fix which according to the pilot does not exist. After landing the pilot's boss calls approach control and finds out they are still using expired charts.
Narrative: Around XA00 I was flying to HNZ with my IFR student. We filed a flight plan to HNZ then back to ZZZ for a 2 hour flight. We were with Raleigh Approach receiving vectors for the RNAV GPS for Runway 24 at HNZ. The controller advised me to proceed direct to a point which I could not locate. I responded to her that I cannot go direct because I cannot find this fix. She just kept telling me to go direct to this imaginary fix; so I just went direct to the IAF for the approach. She said nothing of it so I assumed the point I went to was correct. After the RNAV 24 approach we wanted vectors to shoot the RNAV 6 back in. Instead of going to the IAF and doing a course reversal the controller advised us to go outbound to TUCOV. TUCOV does not exist. We just went outbound until we crossed Virginia and I took controls and turned around inbound; I heard nothing from the controller and he cleared me in for the approach. Why would a controller have me fly outbound when I am on the course to do a course reversal is what I was wondering about. After the approach we headed back to ZZZ. I spoke to my boss and we called the Raleigh approach on the telephone. Turns out that the controllers had expired charts; hence the reason we had this confusion.
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.