Narrative:

After being cleared for visual approach to gvl, was switched to unicom and canceled IFR. After switching to unicom at approximately 5 NM from field on a straight-in approach, broadcast aircraft identify, location, and intentions (straight-in full stop). No aircraft responded to position call. Repeated call at 3 NM straight-in and approximately 3/4 -1 mi final -- again no response to radio xmissions. (WX conditions: VFR, clear, 8 mi visibility, winds variable at 5 KTS.) after touchdown during rollout, I saw the other aircraft (bonanza) on about a 1/4 mi final to the opposite runway (aircraft nose-to-nose). Broadcast on unicom that an aircraft was on the runway to go around. At approximately the threshold at the opposite runway, the bonanza executed a go around. Estimate that go around was initiated approximately 1000-2000 ft away. Bonanza crossed over my aircraft at approximately 200 ft. After parking aircraft, we were informed that the unicom frequency had been changed as of XA00 the previous day. No NOTAMS were found addressing the change in unicom frequency. In discussion with the airfield manager, he commented 'we anticipated this kind of situation.' but obviously he did not take appropriate steps to prevent it. By issuing a clearly worded NOTAM that the unicom frequency had changed or including the change in frequency on the AWOS, this situation could have been avoided. Callback conversation with reporter revealed the following information: in communication with the flight information design analyst at the commercial chart publisher. He indicated the NOTAM flight data digest #207 did not issue the change until oct/xa/02. The publisher has issued a NOTAM which will be published nov/xa/02. The plate page information will be released nov/xi/02 for the dec/xa/02 revision. The analyst does not know why the NOTAM flight data digest took so long to release the frequency change.

Related reports:

Google
 

Original NASA ASRS Text

Title: SA226 CREW HAD A BE35 ON SHORT FINAL APCH, LNDG NOSE-TO-NOSE AT GVL.

Narrative: AFTER BEING CLRED FOR VISUAL APCH TO GVL, WAS SWITCHED TO UNICOM AND CANCELED IFR. AFTER SWITCHING TO UNICOM AT APPROX 5 NM FROM FIELD ON A STRAIGHT-IN APCH, BROADCAST ACFT IDENT, LOCATION, AND INTENTIONS (STRAIGHT-IN FULL STOP). NO ACFT RESPONDED TO POS CALL. REPEATED CALL AT 3 NM STRAIGHT-IN AND APPROX 3/4 -1 MI FINAL -- AGAIN NO RESPONSE TO RADIO XMISSIONS. (WX CONDITIONS: VFR, CLR, 8 MI VISIBILITY, WINDS VARIABLE AT 5 KTS.) AFTER TOUCHDOWN DURING ROLLOUT, I SAW THE OTHER ACFT (BONANZA) ON ABOUT A 1/4 MI FINAL TO THE OPPOSITE RWY (ACFT NOSE-TO-NOSE). BROADCAST ON UNICOM THAT AN ACFT WAS ON THE RWY TO GO AROUND. AT APPROX THE THRESHOLD AT THE OPPOSITE RWY, THE BONANZA EXECUTED A GAR. ESTIMATE THAT GAR WAS INITIATED APPROX 1000-2000 FT AWAY. BONANZA CROSSED OVER MY ACFT AT APPROX 200 FT. AFTER PARKING ACFT, WE WERE INFORMED THAT THE UNICOM FREQ HAD BEEN CHANGED AS OF XA00 THE PREVIOUS DAY. NO NOTAMS WERE FOUND ADDRESSING THE CHANGE IN UNICOM FREQ. IN DISCUSSION WITH THE AIRFIELD MGR, HE COMMENTED 'WE ANTICIPATED THIS KIND OF SIT.' BUT OBVIOUSLY HE DID NOT TAKE APPROPRIATE STEPS TO PREVENT IT. BY ISSUING A CLRLY WORDED NOTAM THAT THE UNICOM FREQ HAD CHANGED OR INCLUDING THE CHANGE IN FREQ ON THE AWOS, THIS SIT COULD HAVE BEEN AVOIDED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: IN COM WITH THE FLT INFO DESIGN ANALYST AT THE COMMERCIAL CHART PUBLISHER. HE INDICATED THE NOTAM FLT DATA DIGEST #207 DID NOT ISSUE THE CHANGE UNTIL OCT/XA/02. THE PUBLISHER HAS ISSUED A NOTAM WHICH WILL BE PUBLISHED NOV/XA/02. THE PLATE PAGE INFO WILL BE RELEASED NOV/XI/02 FOR THE DEC/XA/02 REVISION. THE ANALYST DOES NOT KNOW WHY THE NOTAM FLT DATA DIGEST TOOK SO LONG TO RELEASE THE FREQ CHANGE.

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.