37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 187004 |
Time | |
Date | 199108 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : 3g8 |
State Reference | NY |
Altitude | msl bound lower : 2400 msl bound upper : 2400 |
Environment | |
Flight Conditions | Marginal |
Light | Dusk |
Aircraft 1 | |
Controlling Facilities | tracon : roc |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Flight Phase | descent : approach descent other landing : go around |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 300 flight time total : 1640 flight time type : 100 |
ASRS Report | 187004 |
Person 2 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I departed 5g0 for a 10 min flight to batavia, ny, 3g8, was cleared to 4000 MSL, reached 3200, then told to descend to 2800, then 2400 and expect ILS 28 at 3g8. Cleared for the ILS to maintain 2400 until established. I turned inbound on the localizer and was advised airport 12 O'clock and 5 mi. I reported not in sight and requested to stay on approach frequency a little further. I was established on localizer and told airport was 12 O'clock and 4 mi and to switch to advisory. Then approach said 'I was 1/2 mi west of batavia' and to contact advisory. I knew I could descend since I was past the final approach fix and started my descent. My GS was inoperative so I used s-loc 28 min but became concerned I was past the airport because of the last approach transmission. I then started to execute a missed approach and was told by approach I was 3-5 mi east of the airport. The approach controller said or meant I was 1/2 mi west of tavia the name of the OM I realized on my next approach. The similarity between the airport name and OM is too close and can be misconstrued. I talked with another pilot of a light twin who landed after me and was told he had heard this confusion before. I was concerned over the matter and called roc approach and talked with the controller. I explained the confusion and he said he had no problem with it or me, but wondered why the botched approach. I believe if the language used would have been 1/2 mi west of the OM, no confusion would have occurred I would have flown my localizer approach till airport on time. But 1/2 mi west of (ba)tavia? Made me think he observed me passing over the airport. An important factor too is I did not know the GS in the aircraft was inoperative until on the approach and had no time to let approach know because I went missed so early. A lag time of a couple mins occurred before I was able to communication to roc approach that I was going missed because of the light twin behind me working with approach. All this occurred in VFR conditions 3 mi visibility and cloud clrncs but on an IFR flight plan. The airport is commonly called batavia and or genesee county and this calling of batavia is wrong.
Original NASA ASRS Text
Title: GA SMA STARTED GAR BEFORE MISSED APCH ON IAP ILS. GS OUT IN VMC WX.
Narrative: I DEPARTED 5G0 FOR A 10 MIN FLT TO BATAVIA, NY, 3G8, WAS CLRED TO 4000 MSL, REACHED 3200, THEN TOLD TO DSND TO 2800, THEN 2400 AND EXPECT ILS 28 AT 3G8. CLRED FOR THE ILS TO MAINTAIN 2400 UNTIL ESTABLISHED. I TURNED INBOUND ON THE LOC AND WAS ADVISED ARPT 12 O'CLOCK AND 5 MI. I RPTED NOT IN SIGHT AND REQUESTED TO STAY ON APCH FREQ A LITTLE FURTHER. I WAS ESTABLISHED ON LOC AND TOLD ARPT WAS 12 O'CLOCK AND 4 MI AND TO SWITCH TO ADVISORY. THEN APCH SAID 'I WAS 1/2 MI W OF BATAVIA' AND TO CONTACT ADVISORY. I KNEW I COULD DSND SINCE I WAS PAST THE FINAL APCH FIX AND STARTED MY DSCNT. MY GS WAS INOP SO I USED S-LOC 28 MIN BUT BECAME CONCERNED I WAS PAST THE ARPT BECAUSE OF THE LAST APCH XMISSION. I THEN STARTED TO EXECUTE A MISSED APCH AND WAS TOLD BY APCH I WAS 3-5 MI E OF THE ARPT. THE APCH CTLR SAID OR MEANT I WAS 1/2 MI W OF TAVIA THE NAME OF THE OM I REALIZED ON MY NEXT APCH. THE SIMILARITY BTWN THE ARPT NAME AND OM IS TOO CLOSE AND CAN BE MISCONSTRUED. I TALKED WITH ANOTHER PLT OF A LIGHT TWIN WHO LANDED AFTER ME AND WAS TOLD HE HAD HEARD THIS CONFUSION BEFORE. I WAS CONCERNED OVER THE MATTER AND CALLED ROC APCH AND TALKED WITH THE CTLR. I EXPLAINED THE CONFUSION AND HE SAID HE HAD NO PROBLEM WITH IT OR ME, BUT WONDERED WHY THE BOTCHED APCH. I BELIEVE IF THE LANGUAGE USED WOULD HAVE BEEN 1/2 MI W OF THE OM, NO CONFUSION WOULD HAVE OCCURRED I WOULD HAVE FLOWN MY LOC APCH TILL ARPT ON TIME. BUT 1/2 MI W OF (BA)TAVIA? MADE ME THINK HE OBSERVED ME PASSING OVER THE ARPT. AN IMPORTANT FACTOR TOO IS I DID NOT KNOW THE GS IN THE ACFT WAS INOP UNTIL ON THE APCH AND HAD NO TIME TO LET APCH KNOW BECAUSE I WENT MISSED SO EARLY. A LAG TIME OF A COUPLE MINS OCCURRED BEFORE I WAS ABLE TO COM TO ROC APCH THAT I WAS GOING MISSED BECAUSE OF THE LIGHT TWIN BEHIND ME WORKING WITH APCH. ALL THIS OCCURRED IN VFR CONDITIONS 3 MI VISIBILITY AND CLOUD CLRNCS BUT ON AN IFR FLT PLAN. THE ARPT IS COMMONLY CALLED BATAVIA AND OR GENESEE COUNTY AND THIS CALLING OF BATAVIA IS WRONG.
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.