Date: 201509
Local time of day: 1201-1800
Location: HYR.Airport, WI
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class E ZMP
ATC / advisory: CTAF HYR
Second aircraft: Small Aircraft; Low Wing; 2 Eng; Retractable Gear
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Time Pressure; Situational Awareness; Communication Breakdown
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Chart Or Publication; Human Factors; Procedure; Airport
Primary problem: Human Factors

Narrative: I was operating my aircraft in the airport's traffic pattern practicing takeoffs and landings; announcing using the CTAF upon my departure 'closed traffic for Runway 3.' The airport was VFR. Immediately prior to this incident; I had made two landings; announcing my position on the CTAF at all key points in the traffic pattern. As I was departing for my third practice landing; I heard another aircraft announce their position '10 north of the airport.' This call was answered by [somebody] who announced winds that favored landing on Runway 3. With increasing vigilance; I looked for this aircraft as I flew the traffic pattern but did not make visual contact with it. I continued to announce my position; including 'turning final for Runway 3.' As my aircraft was almost touching down on Runway 3; I suddenly heard a call on CTAF; something to the effect 'NXXXXX you have an aircraft coming at you; get off the runway immediately.' I opened the throttle and as I gained flying speed climbed from the runway at a sharp angle to it so as to avoid the on-coming aircraft which had landed on Runway 21 in the opposite direction I was departing.Upon landing; I questioned the pilot of this aircraft to understand what factors caused his aircraft to land in the opposite direction. That pilot explained he had just executed a missed approach at another airport approximately 38nm to the northeast because it was below approach minimums. His alternate was also below minimums. Whether using ATC guidance or his own navigation; he then selected the airport I was operating at as his new destination; apparently proceeding directly towards it. After his initial position report; I never heard any other transmissions from this aircraft. When I asked if he had checked NOTAMs for this new destination he admitted he had not. Further complicating the issue was the approach charts he was using for this new destination still referred to runway numbers that had been previously changed by the issuance of a NOTAM on May 2015 with an August 2015 expiration. The most recent approach chart cycle released on August still does not reflect the new runway numbers. This pilot admitted hearing me calling my turns in the traffic pattern for Runway 3; but because his approach charts were for Runways 2/20; he believed I was operating at a different airport.This potential accident could have been avoided if the NOTAM system and the approach chart systems were integrated in some way to have each reflect a change simultaneously or at least cause an FDC NOTAM to be issued alerting pilots that the current approach charts for a particular airport do not reflect a future change to the current runway numbers.




Synopsis: A pilot on short final for HYR Runway 3 executed a go around after he was alerted by an individual on the ground about an unannounced aircraft landing Runway 21. The arrival aircraft pilot possessed outdated charts showing Runway 02/20 and did not associate other CTAF calls with HYR Runway 3.