|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : phl|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Controlling Facilities||tower : phl|
|Operator||general aviation : corporate|
|Make Model Name||Small Transport, Low Wing, 2 Turboprop Eng|
|Flight Phase||descent : approach|
|Route In Use||enroute : on vectors|
|Function||flight crew : single pilot|
|Qualification||pilot : atp|
|Experience||flight time last 90 days : 55|
flight time total : 8020
flight time type : 240
|Affiliation||government : faa|
|Function||controller : local|
|Qualification||controller : non radar|
|Anomaly||other anomaly other|
|Independent Detector||other flight crewa|
|Resolutory Action||none taken : detected after the fact|
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||Pilot Deviation|
The flight was a business trip from C65 to ilg with a flight plan filed with terre haute FSS in the early morning. Departure was made from C65 and clearance received from ZAU clearing us present position (40 mi east of southbend) direct to ilg. About 150 mi down the trip we received new clearance present position direct wheeling direct ilg. Another 100 mi down the trip we received a new clearance present position to ravine VOR direct bucks intersection direct ilg. About 60 mi west of ilg I received ATIS for ilg of 25000' scattered, 4 mi fog, using runway 1 ILS. I acknowledged the ILS 110.3 into my RNAV for later use and center turned me over to phl approach. The controller came back to me very fast with a radar vector and the words 'expect the ILS,' not expect the ILS 27 at international. Since I was given radar vectors, I changed over my RNAV to the ILS for runway 1 ilg. I also set up the beacon at ilg ILS runway 1 on the ADF. I received more vectors, and the vectors were not really making much sense for lining up for the ILS 1 at ilg. After more vectors, the controller said 'expect 27R.' I looked at the charts to see where and what is runway 27. Controller came back now with, 'I'm gonna take you in close to the marker now and turn to 290 degrees, cleared for ILS 27.' I had already changed my RNAV over to a VOR runway 27 approach at ilg because of the 'expect 27R,' and he cleared me for ILS 27. I looked in the chart book and found no ILS 27 to ilg. Now VFR and clear of clouds, I called 'airport in sight,' and I was cleared to land. On 1 mi final I saw all of the commuter planes on ramp and I thought, ' boy, I don't remember any commercial operation at ilg,' but I hadn't been to ilg for a yr or 2. I landed and asked for taxi to FBO aviation. Cleared to FBO and then I realized I was not at ilg! I think with all the similarity of the airports, with the radar vectors and runway layouts, the lack of detail in information being transmitted by the controller and the congestion of the controller's area, everything just went wrong. The only thing that I can't understand is what destination was on my flight plan slip in the tower. If it was phl, who put it there, when and why? Yes, my boss was not impressed.
Original NASA ASRS Text
Title: SINGLE PLT CORP TWIN ENGINE TURBOPROP RECEIVES RADAR VECTORS TO AN ILS AT PHL INSTEAD OF THE INTENDED AND FILED DESTINATION ILG.
Narrative: THE FLT WAS A BUSINESS TRIP FROM C65 TO ILG WITH A FLT PLAN FILED WITH TERRE HAUTE FSS IN THE EARLY MORNING. DEP WAS MADE FROM C65 AND CLRNC RECEIVED FROM ZAU CLRING US PRESENT POS (40 MI E OF SOUTHBEND) DIRECT TO ILG. ABOUT 150 MI DOWN THE TRIP WE RECEIVED NEW CLRNC PRESENT POS DIRECT WHEELING DIRECT ILG. ANOTHER 100 MI DOWN THE TRIP WE RECEIVED A NEW CLRNC PRESENT POS TO RAVINE VOR DIRECT BUCKS INTXN DIRECT ILG. ABOUT 60 MI W OF ILG I RECEIVED ATIS FOR ILG OF 25000' SCATTERED, 4 MI FOG, USING RWY 1 ILS. I ACKNOWLEDGED THE ILS 110.3 INTO MY RNAV FOR LATER USE AND CENTER TURNED ME OVER TO PHL APCH. THE CTLR CAME BACK TO ME VERY FAST WITH A RADAR VECTOR AND THE WORDS 'EXPECT THE ILS,' NOT EXPECT THE ILS 27 AT INTL. SINCE I WAS GIVEN RADAR VECTORS, I CHANGED OVER MY RNAV TO THE ILS FOR RWY 1 ILG. I ALSO SET UP THE BEACON AT ILG ILS RWY 1 ON THE ADF. I RECEIVED MORE VECTORS, AND THE VECTORS WERE NOT REALLY MAKING MUCH SENSE FOR LINING UP FOR THE ILS 1 AT ILG. AFTER MORE VECTORS, THE CTLR SAID 'EXPECT 27R.' I LOOKED AT THE CHARTS TO SEE WHERE AND WHAT IS RWY 27. CTLR CAME BACK NOW WITH, 'I'M GONNA TAKE YOU IN CLOSE TO THE MARKER NOW AND TURN TO 290 DEGS, CLRED FOR ILS 27.' I HAD ALREADY CHANGED MY RNAV OVER TO A VOR RWY 27 APCH AT ILG BECAUSE OF THE 'EXPECT 27R,' AND HE CLRED ME FOR ILS 27. I LOOKED IN THE CHART BOOK AND FOUND NO ILS 27 TO ILG. NOW VFR AND CLR OF CLOUDS, I CALLED 'ARPT IN SIGHT,' AND I WAS CLRED TO LAND. ON 1 MI FINAL I SAW ALL OF THE COMMUTER PLANES ON RAMP AND I THOUGHT, ' BOY, I DON'T REMEMBER ANY COMMERCIAL OPERATION AT ILG,' BUT I HADN'T BEEN TO ILG FOR A YR OR 2. I LANDED AND ASKED FOR TAXI TO FBO AVIATION. CLRED TO FBO AND THEN I REALIZED I WAS NOT AT ILG! I THINK WITH ALL THE SIMILARITY OF THE ARPTS, WITH THE RADAR VECTORS AND RWY LAYOUTS, THE LACK OF DETAIL IN INFO BEING XMITTED BY THE CTLR AND THE CONGESTION OF THE CTLR'S AREA, EVERYTHING JUST WENT WRONG. THE ONLY THING THAT I CAN'T UNDERSTAND IS WHAT DEST WAS ON MY FLT PLAN SLIP IN THE TWR. IF IT WAS PHL, WHO PUT IT THERE, WHEN AND WHY? YES, MY BOSS WAS NOT IMPRESSED.
Data retrieved from NASA's ASRS site as of July 2007 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.