A single engine instructor pilot reported landing on CTAF lwb runway 22 and taking evasive action be...

Narrative:

Arrived at lwb in perfect VFR conditions. Tower opens at XA00AM local and AWOS reported wind calm; 10 SM visibility skc. There were numerous aircraft on the CTAF announcing their distance from lwb and it appeared that my partner (flying) and I were #1 for the airport. Arriving from the south; we announced and entered a left downwind for runway 22. We observed no traffic ahead of us or anyone announcing a position ahead of us. Called left base to runway 22 and final for runway 11 on CTAF. We both had verified that we were on the correct frequency and were hearing numerous other aircraft announcing their arrival at lwb. Landed normally on the 7000 ft by 150 ft runway; which has several slight elevation changes along its length. Upon cresting the first elevation change; I observed another aircraft on the runway heading toward us. I took control of the aircraft and steering to the left of the runway; as it appeared that the other aircraft was also heading to the left edge in the opposite direction. At that time I thought that the other aircraft was back-taxiing to runway 22 on the runway rather than the taxiway. I made a radio call on the CTAF to the aircraft following me that there was an aircraft on the runway; back-taxiing; apparently not broadcasting on the CTAF. Several acknowledged my transmission. We passed each other in the opposite direction; on the left edge of the runway without incident. I later encountered the other pilot and learned that he had actually landed on runway 4. I told him (amicably) that I had not heard any transmission from him on CTAF. He said that he had been cleared for a visual approach to runway 4; and heard no transmission on CTAF. I have to believe that he hadn't changed from air traffic control to CTAF. One cannot ever be too vigilant at any airport; especially when there is no operating control panel.

Original NASA ASRS Text

Title: A single engine instructor pilot reported landing on CTAF LWB Runway 22 and taking evasive action because of an aircraft that landed on Runway 4. The Runway 4 traffic apparently did not make CTAF airport traffic reports.

Narrative: Arrived at LWB in perfect VFR conditions. Tower opens at XA00AM local and AWOS reported wind calm; 10 SM visibility SKC. There were numerous aircraft on the CTAF announcing their distance from LWB and it appeared that my partner (flying) and I were #1 for the airport. Arriving from the south; we announced and entered a Left downwind for Runway 22. We observed no traffic ahead of us or anyone announcing a position ahead of us. Called Left base to Runway 22 and final for Runway 11 on CTAF. We both had verified that we were on the correct frequency and were hearing numerous other aircraft announcing their arrival at LWB. Landed normally on the 7000 FT by 150 FT runway; which has several slight elevation changes along its length. Upon cresting the first elevation change; I observed another aircraft on the Runway heading toward us. I took control of the aircraft and steering to the left of the Runway; as it appeared that the other aircraft was also heading to the left edge in the opposite direction. At that time I thought that the other aircraft was back-taxiing to Runway 22 on the runway rather than the taxiway. I made a radio call on the CTAF to the aircraft following me that there was an aircraft on the runway; back-taxiing; apparently not broadcasting on the CTAF. Several acknowledged my transmission. We passed each other in the opposite direction; on the left edge of the runway without incident. I later encountered the other pilot and learned that he had actually landed on Runway 4. I told him (amicably) that I had not heard any transmission from him on CTAF. He said that he had been cleared for a visual approach to Runway 4; and heard no transmission on CTAF. I have to believe that he hadn't changed from air traffic control to CTAF. One cannot ever be too vigilant at any airport; especially when there is no operating control panel.

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

Attributes
ACN	841723
Time
Date	200906
Local Time Of Day	0601-1200
Place
Locale Reference	LWB.Airport
State Reference	WV
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Landing
Flight Plan	VFR
Aircraft 2
Make Model Name	Small Aircraft
Operating Under FAR Part	Part 91
Flight Phase	Landing
Route In Use	Direct
Flight Plan	IFR
Component
Aircraft Component	VHF
Person 1
Function	Instructor Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 130 Flight Crew Total 6270 Flight Crew Type 1600
Events
Anomaly	Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Event / Encounter Aircraft Ground Excursion Runway
Miss Distance	Horizontal 50

A single engine instructor pilot reported landing on CTAF lwb runway 22 and taking evasive action because of an aircraft that landed on runway 4. The runway 4 traffic apparently did not make CTAF airport traffic reports.