37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1191826 |
Time | |
Date | 201407 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | UWL.Airport |
State Reference | IN |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Direct |
Flight Plan | IFR |
Person 1 | |
Function | Instructor |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 7600 Flight Crew Type 500 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance |
Narrative:
We were on an IFR flight plan to uwl. Filed route of flight was ZZZ rid econo. Econo is the only IAF on the approach VOR or GPS 27 uwl. Crossing rid were still talking to columbus approach and columbus approach cleared us for the VOR 27 approach. The plate shows a bold hold at econo and does not state 'no pt' at rid VOR. But going straight in from rid I queried approach control to ask if we could go straight in or if they needed us to fly the mandatory hold at econo. The controller then asked us what approach we were on. I reminded him that he had cleared us for VOR 27 at new castle. Approach controller responded; 'oh I thought you were doing the VOR 6 at rid. Contact indianapolis approach now on 135.45.' I quickly contacted indianapolis approach and they seemed surprised to hear from us. Indianapolis then re-cleared us for the 'VOR 27 new castle straight in.' in all the flying I've done I've never been handed off from one approach facility to another after having been cleared for the approach. We were in the clouds at the MEA when this occurred; so it was concerning that the columbus approach controller thought we were on a different approach than we were on and then had to hand us off to another sector.
Original NASA ASRS Text
Title: Small Aircraft pilot describes flight where they are cleared for one approach then the Controller asks them what approach they are on. Controller then clarifies in his mind the approach and ships the aircraft to another Approach Control. Pilot questions why they were switched from one Approach Control to another after being cleared for the approach.
Narrative: We were on an IFR flight plan to UWL. Filed route of flight was ZZZ RID ECONO. ECONO is the only IAF on the approach VOR or GPS 27 UWL. Crossing RID were still talking to Columbus Approach and Columbus Approach cleared us for the VOR 27 Approach. The plate shows a bold hold at ECONO and does not state 'No PT' at RID VOR. But going straight in from RID I queried Approach Control to ask if we could go straight in or if they needed us to fly the mandatory hold at ECONO. The Controller then asked us what approach we were on. I reminded him that he had cleared us for VOR 27 at New Castle. Approach Controller responded; 'Oh I thought you were doing the VOR 6 at RID. Contact Indianapolis Approach now on 135.45.' I quickly contacted Indianapolis Approach and they seemed surprised to hear from us. Indianapolis then re-cleared us for the 'VOR 27 New Castle Straight In.' In all the flying I've done I've never been handed off from one approach facility to another after having been cleared for the approach. We were in the clouds at the MEA when this occurred; so it was concerning that the Columbus Approach Controller thought we were on a different approach than we were on and then had to hand us off to another sector.
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.