Narrative:

Between XA00-XB00 a.M. Local time I was returning to based airport (07C) from harrolds private strip northeast near butler, in, where I had the oil changed. Windsock at harrold's (12-15 mi away) indicated mild northeast winds -- departed there runway 36. Morning WX reports were of northeast winds around 8 mph. In approaching town of auburn (approximately 3 mi northwest of town) I called up auburn airport unicom on 123.0 for airport advisory and runway in use -- 'please.' no answer. Called again 5 mi northeast of airport -- no answer. Called 2 1/2 mi out -- no answer. Monitoring of 123.0 heard no other traffic announcing activity at that airport, saw none in sky or on runway from 1800 ft MSL. Based on visible windsock 1 mi out indicating mild northeast winds I entered from the north at 45 degree angle and announced on 123.0 I was 'downwind for runway 9 -- auburn.' no answers. Announced 'left base for runway 9 -- auburn.' no response. Runway has a rise in the 1/2 way point. Just as wheels touched down, saw other aircraft departing runway 27 coming over the rise then slowing and going to right of runway. I'm swerving to a stop. Heard no announcements by other aircraft of taxiing or departure and no anti-collision beacon on to be seen from above. On original departure XX00 a.M. There was no windsock activity and another aircraft had landed on runway 27, so I announced back taxi on runway 27 and departed same. Noting the active may have changed since departure, I was asking for information and got none but not uncommon there to get no response even if the employee may be sitting next to the unicom and not uncommon lately for other pilots to lack courtesy and safety of announcing intentions and position. Other unicom airports too. Suggestions: continued constant alertness at unicom airports and swivel heading and eyeballing. Return to the safety and courtesy of unicoms being answered on request and somehow stop the laxity pilots (students, instructors, everybody I've noted) of not reporting position and intentions. Also better flight instructions regarding airspace communications. Hope this never happens again. I'm still shaking. While putting aircraft away I noted other aircraft continued to depart on runway 27. If that was the downwind active, I wish somebody would have informed me when I called and when I announced position. Callback conversation with reporter revealed the following: reporter indicates not unusual to receive no response on unicom. People can be in office, hear call and just ignore it. Feels it is very unsafe situation. Feels flight school is not teaching appropriate procedures of communicating. Not willing to talk to operators because situation is very political and does not want to jeopardize hangar space.

Related reports:

Google
 

Original NASA ASRS Text

Title: GROUND CONFLICT, OPPOSTIE DIRECTION ON RWY.

Narrative: BTWN XA00-XB00 A.M. LCL TIME I WAS RETURNING TO BASED ARPT (07C) FROM HARROLDS PVT STRIP NE NEAR BUTLER, IN, WHERE I HAD THE OIL CHANGED. WINDSOCK AT HARROLD'S (12-15 MI AWAY) INDICATED MILD NE WINDS -- DEPARTED THERE RWY 36. MORNING WX RPTS WERE OF NE WINDS AROUND 8 MPH. IN APCHING TOWN OF AUBURN (APPROX 3 MI NW OF TOWN) I CALLED UP AUBURN ARPT UNICOM ON 123.0 FOR ARPT ADVISORY AND RWY IN USE -- 'PLEASE.' NO ANSWER. CALLED AGAIN 5 MI NE OF ARPT -- NO ANSWER. CALLED 2 1/2 MI OUT -- NO ANSWER. MONITORING OF 123.0 HEARD NO OTHER TFC ANNOUNCING ACTIVITY AT THAT ARPT, SAW NONE IN SKY OR ON RWY FROM 1800 FT MSL. BASED ON VISIBLE WINDSOCK 1 MI OUT INDICATING MILD NE WINDS I ENTERED FROM THE N AT 45 DEG ANGLE AND ANNOUNCED ON 123.0 I WAS 'DOWNWIND FOR RWY 9 -- AUBURN.' NO ANSWERS. ANNOUNCED 'L BASE FOR RWY 9 -- AUBURN.' NO RESPONSE. RWY HAS A RISE IN THE 1/2 WAY POINT. JUST AS WHEELS TOUCHED DOWN, SAW OTHER ACFT DEPARTING RWY 27 COMING OVER THE RISE THEN SLOWING AND GOING TO R OF RWY. I'M SWERVING TO A STOP. HEARD NO ANNOUNCEMENTS BY OTHER ACFT OF TAXIING OR DEP AND NO ANTI-COLLISION BEACON ON TO BE SEEN FROM ABOVE. ON ORIGINAL DEP XX00 A.M. THERE WAS NO WINDSOCK ACTIVITY AND ANOTHER ACFT HAD LANDED ON RWY 27, SO I ANNOUNCED BACK TAXI ON RWY 27 AND DEPARTED SAME. NOTING THE ACTIVE MAY HAVE CHANGED SINCE DEP, I WAS ASKING FOR INFO AND GOT NONE BUT NOT UNCOMMON THERE TO GET NO RESPONSE EVEN IF THE EMPLOYEE MAY BE SITTING NEXT TO THE UNICOM AND NOT UNCOMMON LATELY FOR OTHER PLTS TO LACK COURTESY AND SAFETY OF ANNOUNCING INTENTIONS AND POS. OTHER UNICOM ARPTS TOO. SUGGESTIONS: CONTINUED CONSTANT ALERTNESS AT UNICOM ARPTS AND SWIVEL HDG AND EYEBALLING. RETURN TO THE SAFETY AND COURTESY OF UNICOMS BEING ANSWERED ON REQUEST AND SOMEHOW STOP THE LAXITY PLTS (STUDENTS, INSTRUCTORS, EVERYBODY I'VE NOTED) OF NOT RPTING POS AND INTENTIONS. ALSO BETTER FLT INSTRUCTIONS REGARDING AIRSPACE COMS. HOPE THIS NEVER HAPPENS AGAIN. I'M STILL SHAKING. WHILE PUTTING ACFT AWAY I NOTED OTHER ACFT CONTINUED TO DEPART ON RWY 27. IF THAT WAS THE DOWNWIND ACTIVE, I WISH SOMEBODY WOULD HAVE INFORMED ME WHEN I CALLED AND WHEN I ANNOUNCED POS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: RPTR INDICATES NOT UNUSUAL TO RECEIVE NO RESPONSE ON UNICOM. PEOPLE CAN BE IN OFFICE, HEAR CALL AND JUST IGNORE IT. FEELS IT IS VERY UNSAFE SIT. FEELS FLT SCHOOL IS NOT TEACHING APPROPRIATE PROCS OF COMMUNICATING. NOT WILLING TO TALK TO OPERATORS BECAUSE SIT IS VERY POLITICAL AND DOES NOT WANT TO JEOPARDIZE HANGAR SPACE.

Data retrieved from NASA's ASRS site as of August 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.