Narrative:

Apr/sun/03, approximately XA00 local: was preparing to return to united states from victoria back course (cyyj). Original intent was to clear us customs at port townsend, wa. Called port townsend customs. A recording indicated the us customs office was closed but off hours and weekend service could be obtained by calling the agent at his home. The phone was continuously busy for well over an hour. Deviated from intentions and called us customs at port angeles. Gave approximately time of arrival of XC30 local and was told XD00 local would be more fitting to their schedule. References to port angeles with us customs, FSS, and other pilots were always port angeles not fairchild or fairchild international. Idented port angeles on the seattle sectional chart as the airport idented as port angeles and took mental note of airport identifier, altitude, runway length, and communication frequency. Called seattle FSS to obtain WX briefing, NOTAMS, and file a VFR flight plan, several us customs and canadian documents read, for return flts to us, a us flight plan needs to be filed. Was told that had changed and a flight plan needed to be filed through a canadian FSS. Called kamloops FSS to obtain WX briefing, NOTAMS, and filed a VFR flight plan to port angeles with an estimated time of departure of XA15 local and 40 min en route. No specific airport identifiers were used by the FSS briefer or me. Preflted and entered the observed now as know into the GPS as the goto location. Obtained a departure clearance from cyyj clearance delivery, received taxi instructions and clearance from ground, taxied to the run-up area as instructed, performed run-up, contacted the tower as being ready for takeoff and departed as instructed from clearance delivery. This departure took the aircraft over the darcy island area. Then proceeded toward port angeles at 2000 ft due to low ceiling of 3000 ft around the victoria island vicinity. Skies were clear several mi south of the island all the way to port angeles. Maintained 2000 ft for the duration of the flight. Reading the seattle sectional in the plane showed port angeles had no WX or barometric information immediately available. This information was obtained from fairchild ASOS. The ASOS information indicated that the wind was coming 5-7 KTS from an easterly direction making a landing in an easterly direction into the wind the preferred choice. As I approach the airport from 7-10 NM out I announced my position and intentions on the port angeles unicom frequency, which is also the frequency for fairchild and started a descent to pattern altitude. As approaching on a 45 degrees for a left downwind for an easterly landing I was able to identify the runway number (runway 7) for the prevailing wind, I announced my intentions on the 45 degrees for runway 7 and continued to announce on downwind entry, downwind, base and final. While about to turn base another aircraft came on frequency and indicated he was further out and not in the immediate vicinity of the airport but was setting up to do a westerly landing on runway 26. I did not do the math in my head to realize runway 7 was not the reciprocal of runway 26 and no one (if anyone) listening on the ground or this aircraft indicated to me that I was using an incorrect runway number in my announcements. The other aircraft continued to announce his intentions as he approached the airport. After landing I was taxiing down the runway looking for the us customs facility but saw no signage indicating anything. I taxied off at the right apron 3/4 of the way down from the approach end of runway 7 in front of a large building on the right side of the apron and right side of the runway. As the other aircraft was announcing a landing from the other direction I turned my aircraft away from the building and faced the approach end of runway I believed the other aircraft would be using for visibility and safety. I saw no other aircraft in the pattern. I asked the other pilot if he knew where the us customs facilities were on the field. He indicated he would be on the ground shortly and I could follow him. His tone and manor indicated to me he was familiar with the airport and facilities. I indicated that I did not have him in sight and he asked where I was on the field. I gave a brief description and he indicated he did not see me on the field and was I sure I was where I thought I was and was I maybe on the grounds of the military facility. I indicated I didn't think so but started a more careful observation. This time bending down and looking up under the high wing and behind at the building I had faced the aircraft away from, and at this time did indeed see the familiar military lettering and insignia. These were not visible from the runway 7 approach end and were not visible while on the 45 degree left traffic entry position for runway 7 because of the acute slant angle to the side of the building with the lettering and insignia. I prepared to depart the facility but personnel finally came out and indicated I shut down. I did as I was told and followed all personnel instructions. I didn't get any names of personnel but assume the individual who took charge was the od. We were directed inside the facility and gave him my name and phone number and that of my passenger as instructed. We were then given permission to leave and we got the correct airport location of the correct airport. We departed and made the proper calls, entries, and landing at fairchild to clear customs. The landing and subsequent takeoff at the military facility were performed with no danger to any persons or property. Contributing factors: 20/20 hindsight would indicate I was overly concerned about clearing us customs properly and the change in the us customs airport added to the stress. I had never pilot'ed an aircraft out of the country and wanted to make sure there were no issues. This stress caused me to overlook flight-planning items I am normally very thorough about, particularly in getting all available information about airports of intended use. All information about airports of intended use was obtained before even starting the flight from my base airport. This information was obtained online from a flight planning sight airport directory. Port angeles was not obtained when doing the overall planning because it was not an airport of intended use. I didn't have access to online services or an airport directory when the deviation from port townsend occurred. On the chart the longitudinal line of 123.30 obliterates the 'I' in international of fairchild international so visually the name of the airport was fairchild ntl (clm). The airport information for fairchild is magenta lettering on varying hues of green, yellow, varying black lines and some information is also obliterated by the class east surface airspace magenta dashed line. Mentally this now becomes just another airport located at the town of port angeles. Care should be taken when charts are published that other items on the chart do not obliterate significant letters in an airport's name especially with a letter such as 'I.' the cgas of port angeles cgas is broken to the second line from the airport name of port angeles so it becomes insignificant to the mind's eye because the airport name port angeles has been discovered. Airport military use designation such as: cgas, AFB, etc, should not by themselves be broken from the airport name unless the airport name is to be broken. The military use designation should be kept with the airport name or a part of the airport name. The legend on the chart for military use designation reads: all military airports are idented by abbreviations AFB, NAS, aaf, etc. For complete information consult DOD FLIP. The military is a big enough entity that gcas should also appear in the legend text. I only saw the one sign on the facilities buildings designating its ownership. There may be more but I didn't see them from my approach. The runway and taxiway was not stenciled with the facility name either. The airport symbol on the chart is identical to the symbol representation for any other GA airport. The only time there is a display of 2 circles to designate a military use airport is if the airport is other than hard surfaced. With the advent of post 9/tue/01 tsa all military airports need to be designated differently on the charts so they can be easily visually idented on the chart. Both facilities use the same frequency. No ground monitoring of the frequency is being done at either facility to avoid confusion of 2 airports being in such close proximity. If the military is going to use a unicom frequency instead of a tower they should monitor the frequency and have someone looking out the window once in a while. At least with a tower, tower personnel may have been astute enough to position a red light on an approaching aircraft not on frequency or indicate to an aircraft on the tower frequency that the airport of intended use is not a GA airport.

Google
 

Original NASA ASRS Text

Title: C172 CESSNA PLT MISTAKES PORT ANGELES CGAS (KNOW) FOR FAIRCHILD INTL ARPT (KCLM) AND LANDS AT WRONG ARPT.

Narrative: APR/SUN/03, APPROX XA00 LCL: WAS PREPARING TO RETURN TO UNITED STATES FROM VICTORIA BC (CYYJ). ORIGINAL INTENT WAS TO CLR US CUSTOMS AT PORT TOWNSEND, WA. CALLED PORT TOWNSEND CUSTOMS. A RECORDING INDICATED THE US CUSTOMS OFFICE WAS CLOSED BUT OFF HRS AND WEEKEND SVC COULD BE OBTAINED BY CALLING THE AGENT AT HIS HOME. THE PHONE WAS CONTINUOUSLY BUSY FOR WELL OVER AN HR. DEVIATED FROM INTENTIONS AND CALLED US CUSTOMS AT PORT ANGELES. GAVE APPROX TIME OF ARR OF XC30 LCL AND WAS TOLD XD00 LCL WOULD BE MORE FITTING TO THEIR SCHEDULE. REFS TO PORT ANGELES WITH US CUSTOMS, FSS, AND OTHER PLTS WERE ALWAYS PORT ANGELES NOT FAIRCHILD OR FAIRCHILD INTL. IDENTED PORT ANGELES ON THE SEATTLE SECTIONAL CHART AS THE ARPT IDENTED AS PORT ANGELES AND TOOK MENTAL NOTE OF ARPT IDENTIFIER, ALT, RWY LENGTH, AND COM FREQ. CALLED SEATTLE FSS TO OBTAIN WX BRIEFING, NOTAMS, AND FILE A VFR FLT PLAN, SEVERAL US CUSTOMS AND CANADIAN DOCUMENTS READ, FOR RETURN FLTS TO US, A US FLT PLAN NEEDS TO BE FILED. WAS TOLD THAT HAD CHANGED AND A FLT PLAN NEEDED TO BE FILED THROUGH A CANADIAN FSS. CALLED KAMLOOPS FSS TO OBTAIN WX BRIEFING, NOTAMS, AND FILED A VFR FLT PLAN TO PORT ANGELES WITH AN ESTIMATED TIME OF DEP OF XA15 LCL AND 40 MIN ENRTE. NO SPECIFIC ARPT IDENTIFIERS WERE USED BY THE FSS BRIEFER OR ME. PREFLTED AND ENTERED THE OBSERVED NOW AS KNOW INTO THE GPS AS THE GOTO LOCATION. OBTAINED A DEP CLRNC FROM CYYJ CLRNC DELIVERY, RECEIVED TAXI INSTRUCTIONS AND CLRNC FROM GND, TAXIED TO THE RUN-UP AREA AS INSTRUCTED, PERFORMED RUN-UP, CONTACTED THE TWR AS BEING READY FOR TKOF AND DEPARTED AS INSTRUCTED FROM CLRNC DELIVERY. THIS DEP TOOK THE ACFT OVER THE DARCY ISLAND AREA. THEN PROCEEDED TOWARD PORT ANGELES AT 2000 FT DUE TO LOW CEILING OF 3000 FT AROUND THE VICTORIA ISLAND VICINITY. SKIES WERE CLR SEVERAL MI S OF THE ISLAND ALL THE WAY TO PORT ANGELES. MAINTAINED 2000 FT FOR THE DURATION OF THE FLT. READING THE SEATTLE SECTIONAL IN THE PLANE SHOWED PORT ANGELES HAD NO WX OR BAROMETRIC INFO IMMEDIATELY AVAILABLE. THIS INFO WAS OBTAINED FROM FAIRCHILD ASOS. THE ASOS INFO INDICATED THAT THE WIND WAS COMING 5-7 KTS FROM AN EASTERLY DIRECTION MAKING A LNDG IN AN EASTERLY DIRECTION INTO THE WIND THE PREFERRED CHOICE. AS I APCH THE ARPT FROM 7-10 NM OUT I ANNOUNCED MY POS AND INTENTIONS ON THE PORT ANGELES UNICOM FREQ, WHICH IS ALSO THE FREQ FOR FAIRCHILD AND STARTED A DSCNT TO PATTERN ALT. AS APCHING ON A 45 DEGS FOR A L DOWNWIND FOR AN EASTERLY LNDG I WAS ABLE TO IDENT THE RWY NUMBER (RWY 7) FOR THE PREVAILING WIND, I ANNOUNCED MY INTENTIONS ON THE 45 DEGS FOR RWY 7 AND CONTINUED TO ANNOUNCE ON DOWNWIND ENTRY, DOWNWIND, BASE AND FINAL. WHILE ABOUT TO TURN BASE ANOTHER ACFT CAME ON FREQ AND INDICATED HE WAS FURTHER OUT AND NOT IN THE IMMEDIATE VICINITY OF THE ARPT BUT WAS SETTING UP TO DO A WESTERLY LNDG ON RWY 26. I DID NOT DO THE MATH IN MY HEAD TO REALIZE RWY 7 WAS NOT THE RECIPROCAL OF RWY 26 AND NO ONE (IF ANYONE) LISTENING ON THE GND OR THIS ACFT INDICATED TO ME THAT I WAS USING AN INCORRECT RWY NUMBER IN MY ANNOUNCEMENTS. THE OTHER ACFT CONTINUED TO ANNOUNCE HIS INTENTIONS AS HE APCHED THE ARPT. AFTER LNDG I WAS TAXIING DOWN THE RWY LOOKING FOR THE US CUSTOMS FACILITY BUT SAW NO SIGNAGE INDICATING ANYTHING. I TAXIED OFF AT THE R APRON 3/4 OF THE WAY DOWN FROM THE APCH END OF RWY 7 IN FRONT OF A LARGE BUILDING ON THE R SIDE OF THE APRON AND R SIDE OF THE RWY. AS THE OTHER ACFT WAS ANNOUNCING A LNDG FROM THE OTHER DIRECTION I TURNED MY ACFT AWAY FROM THE BUILDING AND FACED THE APCH END OF RWY I BELIEVED THE OTHER ACFT WOULD BE USING FOR VISIBILITY AND SAFETY. I SAW NO OTHER ACFT IN THE PATTERN. I ASKED THE OTHER PLT IF HE KNEW WHERE THE US CUSTOMS FACILITIES WERE ON THE FIELD. HE INDICATED HE WOULD BE ON THE GND SHORTLY AND I COULD FOLLOW HIM. HIS TONE AND MANOR INDICATED TO ME HE WAS FAMILIAR WITH THE ARPT AND FACILITIES. I INDICATED THAT I DID NOT HAVE HIM IN SIGHT AND HE ASKED WHERE I WAS ON THE FIELD. I GAVE A BRIEF DESCRIPTION AND HE INDICATED HE DID NOT SEE ME ON THE FIELD AND WAS I SURE I WAS WHERE I THOUGHT I WAS AND WAS I MAYBE ON THE GNDS OF THE MIL FACILITY. I INDICATED I DIDN'T THINK SO BUT STARTED A MORE CAREFUL OBSERVATION. THIS TIME BENDING DOWN AND LOOKING UP UNDER THE HIGH WING AND BEHIND AT THE BUILDING I HAD FACED THE ACFT AWAY FROM, AND AT THIS TIME DID INDEED SEE THE FAMILIAR MIL LETTERING AND INSIGNIA. THESE WERE NOT VISIBLE FROM THE RWY 7 APCH END AND WERE NOT VISIBLE WHILE ON THE 45 DEG L TFC ENTRY POS FOR RWY 7 BECAUSE OF THE ACUTE SLANT ANGLE TO THE SIDE OF THE BUILDING WITH THE LETTERING AND INSIGNIA. I PREPARED TO DEPART THE FACILITY BUT PERSONNEL FINALLY CAME OUT AND INDICATED I SHUT DOWN. I DID AS I WAS TOLD AND FOLLOWED ALL PERSONNEL INSTRUCTIONS. I DIDN'T GET ANY NAMES OF PERSONNEL BUT ASSUME THE INDIVIDUAL WHO TOOK CHARGE WAS THE OD. WE WERE DIRECTED INSIDE THE FACILITY AND GAVE HIM MY NAME AND PHONE NUMBER AND THAT OF MY PAX AS INSTRUCTED. WE WERE THEN GIVEN PERMISSION TO LEAVE AND WE GOT THE CORRECT ARPT LOCATION OF THE CORRECT ARPT. WE DEPARTED AND MADE THE PROPER CALLS, ENTRIES, AND LNDG AT FAIRCHILD TO CLR CUSTOMS. THE LNDG AND SUBSEQUENT TKOF AT THE MIL FACILITY WERE PERFORMED WITH NO DANGER TO ANY PERSONS OR PROPERTY. CONTRIBUTING FACTORS: 20/20 HINDSIGHT WOULD INDICATE I WAS OVERLY CONCERNED ABOUT CLRING US CUSTOMS PROPERLY AND THE CHANGE IN THE US CUSTOMS ARPT ADDED TO THE STRESS. I HAD NEVER PLT'ED AN ACFT OUT OF THE COUNTRY AND WANTED TO MAKE SURE THERE WERE NO ISSUES. THIS STRESS CAUSED ME TO OVERLOOK FLT-PLANNING ITEMS I AM NORMALLY VERY THOROUGH ABOUT, PARTICULARLY IN GETTING ALL AVAILABLE INFO ABOUT ARPTS OF INTENDED USE. ALL INFO ABOUT ARPTS OF INTENDED USE WAS OBTAINED BEFORE EVEN STARTING THE FLT FROM MY BASE ARPT. THIS INFO WAS OBTAINED ONLINE FROM A FLT PLANNING SIGHT ARPT DIRECTORY. PORT ANGELES WAS NOT OBTAINED WHEN DOING THE OVERALL PLANNING BECAUSE IT WAS NOT AN ARPT OF INTENDED USE. I DIDN'T HAVE ACCESS TO ONLINE SVCS OR AN ARPT DIRECTORY WHEN THE DEV FROM PORT TOWNSEND OCCURRED. ON THE CHART THE LONGITUDINAL LINE OF 123.30 OBLITERATES THE 'I' IN INTL OF FAIRCHILD INTL SO VISUALLY THE NAME OF THE ARPT WAS FAIRCHILD NTL (CLM). THE ARPT INFO FOR FAIRCHILD IS MAGENTA LETTERING ON VARYING HUES OF GREEN, YELLOW, VARYING BLACK LINES AND SOME INFO IS ALSO OBLITERATED BY THE CLASS E SURFACE AIRSPACE MAGENTA DASHED LINE. MENTALLY THIS NOW BECOMES JUST ANOTHER ARPT LOCATED AT THE TOWN OF PORT ANGELES. CARE SHOULD BE TAKEN WHEN CHARTS ARE PUBLISHED THAT OTHER ITEMS ON THE CHART DO NOT OBLITERATE SIGNIFICANT LETTERS IN AN ARPT'S NAME ESPECIALLY WITH A LETTER SUCH AS 'I.' THE CGAS OF PORT ANGELES CGAS IS BROKEN TO THE SECOND LINE FROM THE ARPT NAME OF PORT ANGELES SO IT BECOMES INSIGNIFICANT TO THE MIND'S EYE BECAUSE THE ARPT NAME PORT ANGELES HAS BEEN DISCOVERED. ARPT MIL USE DESIGNATION SUCH AS: CGAS, AFB, ETC, SHOULD NOT BY THEMSELVES BE BROKEN FROM THE ARPT NAME UNLESS THE ARPT NAME IS TO BE BROKEN. THE MIL USE DESIGNATION SHOULD BE KEPT WITH THE ARPT NAME OR A PART OF THE ARPT NAME. THE LEGEND ON THE CHART FOR MIL USE DESIGNATION READS: ALL MIL ARPTS ARE IDENTED BY ABBREVIATIONS AFB, NAS, AAF, ETC. FOR COMPLETE INFO CONSULT DOD FLIP. THE MIL IS A BIG ENOUGH ENTITY THAT GCAS SHOULD ALSO APPEAR IN THE LEGEND TEXT. I ONLY SAW THE ONE SIGN ON THE FACILITIES BUILDINGS DESIGNATING ITS OWNERSHIP. THERE MAY BE MORE BUT I DIDN'T SEE THEM FROM MY APCH. THE RWY AND TXWY WAS NOT STENCILED WITH THE FACILITY NAME EITHER. THE ARPT SYMBOL ON THE CHART IS IDENTICAL TO THE SYMBOL REPRESENTATION FOR ANY OTHER GA ARPT. THE ONLY TIME THERE IS A DISPLAY OF 2 CIRCLES TO DESIGNATE A MIL USE ARPT IS IF THE ARPT IS OTHER THAN HARD SURFACED. WITH THE ADVENT OF POST 9/TUE/01 TSA ALL MIL ARPTS NEED TO BE DESIGNATED DIFFERENTLY ON THE CHARTS SO THEY CAN BE EASILY VISUALLY IDENTED ON THE CHART. BOTH FACILITIES USE THE SAME FREQ. NO GND MONITORING OF THE FREQ IS BEING DONE AT EITHER FACILITY TO AVOID CONFUSION OF 2 ARPTS BEING IN SUCH CLOSE PROX. IF THE MIL IS GOING TO USE A UNICOM FREQ INSTEAD OF A TWR THEY SHOULD MONITOR THE FREQ AND HAVE SOMEONE LOOKING OUT THE WINDOW ONCE IN A WHILE. AT LEAST WITH A TWR, TWR PERSONNEL MAY HAVE BEEN ASTUTE ENOUGH TO POS A RED LIGHT ON AN APCHING ACFT NOT ON FREQ OR INDICATE TO AN ACFT ON THE TWR FREQ THAT THE ARPT OF INTENDED USE IS NOT A GA ARPT.

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.