Narrative:

On a day flight from chico, ca, to orland, ca, my intention was to shoot touch and go's at orland. Arriving over head the airport, I was unable to get a response from the unicom. The windsock favored the south runway (15). I read the traffic indicator and I interpreted it to require right traffic for runway 15. (I had also observed another aircraft making a right downwind departure.) turning final, we saw a blue small aircraft pass below and behind us -- also landing but making left traffic to runway 15. I had made all the required calls -- downwind, base, and final on the CTAF/unicom and had heard no response from unicom or other traffic. Shortly after the incident, the small aircraft came up on the radio saying that left traffic was the standard for runway 15 orland. I realize now that I looked at the upwind side of the indicator and made right traffic. This is a confusing indication and as a relatively uncurrent GA pilot, I was overconfident and wrong! My error almost caused a midair (no actual maneuvering was involved -- but too close for comfort). When I got home, I also realized that I was carrying a passenger and not current under the 90 day rule. I am a professional airline pilot and I am current on medium large transport, but the last lndgs in an small aircraft were 5 months ago when I was checked out. I used poor judgement and have started to hit the books again -- complacency and overconfidence got me this time. Better than an accident. Callback conversation with reporter revealed the following information: reporter states he has checked all pubs he can think of and finds no reference to the type of markings he saw and has drawn on report. He talked to local pilots who just accept there is left pattern at orland. Unicom is manned on a hit and miss basis so could not get any information from them. Plans to send graphic of traffic pattern indicators to FSDO for an explanation.

Google
 

Original NASA ASRS Text

Title: SMA PLT FOLLOWS TFC PATTERN INDICATOR BUT IS TOLD WRONG DIRECTION PATTERN. NMAC WITH SECOND ACFT.

Narrative: ON A DAY FLT FROM CHICO, CA, TO ORLAND, CA, MY INTENTION WAS TO SHOOT TOUCH AND GO'S AT ORLAND. ARRIVING OVER HEAD THE ARPT, I WAS UNABLE TO GET A RESPONSE FROM THE UNICOM. THE WINDSOCK FAVORED THE S RWY (15). I READ THE TFC INDICATOR AND I INTERPRETED IT TO REQUIRE R TFC FOR RWY 15. (I HAD ALSO OBSERVED ANOTHER ACFT MAKING A R DOWNWIND DEP.) TURNING FINAL, WE SAW A BLUE SMA PASS BELOW AND BEHIND US -- ALSO LNDG BUT MAKING L TFC TO RWY 15. I HAD MADE ALL THE REQUIRED CALLS -- DOWNWIND, BASE, AND FINAL ON THE CTAF/UNICOM AND HAD HEARD NO RESPONSE FROM UNICOM OR OTHER TFC. SHORTLY AFTER THE INCIDENT, THE SMA CAME UP ON THE RADIO SAYING THAT L TFC WAS THE STANDARD FOR RWY 15 ORLAND. I REALIZE NOW THAT I LOOKED AT THE UPWIND SIDE OF THE INDICATOR AND MADE R TFC. THIS IS A CONFUSING INDICATION AND AS A RELATIVELY UNCURRENT GA PLT, I WAS OVERCONFIDENT AND WRONG! MY ERROR ALMOST CAUSED A MIDAIR (NO ACTUAL MANEUVERING WAS INVOLVED -- BUT TOO CLOSE FOR COMFORT). WHEN I GOT HOME, I ALSO REALIZED THAT I WAS CARRYING A PAX AND NOT CURRENT UNDER THE 90 DAY RULE. I AM A PROFESSIONAL AIRLINE PLT AND I AM CURRENT ON MLG, BUT THE LAST LNDGS IN AN SMA WERE 5 MONTHS AGO WHEN I WAS CHKED OUT. I USED POOR JUDGEMENT AND HAVE STARTED TO HIT THE BOOKS AGAIN -- COMPLACENCY AND OVERCONFIDENCE GOT ME THIS TIME. BETTER THAN AN ACCIDENT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES HE HAS CHKED ALL PUBS HE CAN THINK OF AND FINDS NO REF TO THE TYPE OF MARKINGS HE SAW AND HAS DRAWN ON RPT. HE TALKED TO LCL PLTS WHO JUST ACCEPT THERE IS L PATTERN AT ORLAND. UNICOM IS MANNED ON A HIT AND MISS BASIS SO COULD NOT GET ANY INFO FROM THEM. PLANS TO SEND GRAPHIC OF TFC PATTERN INDICATORS TO FSDO FOR AN EXPLANATION.

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.