2 smas had an near midair collision at an uncontrolled airport.

Attributes
ACN	262833
Time
Date	199402
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : 3b1
State Reference	ME
Altitude	msl bound lower : 2500 msl bound upper : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	other
Flight Plan	None
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 200 flight time total : 3800 flight time type : 300
ASRS Report	262833
Person 2
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : private
Events
Anomaly	conflict : nmac non adherence : far non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : insufficient time
Consequence	Other
Miss Distance	horizontal : 0 vertical : 50
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

10 mi from 3b1, unicom was monitored for traffic, but from prior experience of no response from unicom, no call was made for TAS. At roughly 1 mi from airport, normal pattern was about to be entered by flying over field to observe windsock. While crossing downwind course for runway 32, near miss occurred with other aircraft in traffic pattern on downwind for 32. Courses were 90 degrees to each other and other aircraft was at traffic pattern altitude (2400 MSL) and our altitude was approximately 2600 MSL descending. No evasive action was required although miss was approximately 50 ft vertical '0' horizontal. I feel contradicting factors were: 1) neither aircraft, although radio equipped, were announcing position. 2) due to snow on ground and bright skies and color of other aircraft being primarily white, traffic was not easy to see. 3) with no altimeter setting and due to my cross country, flight altitude was not as thought. I feel that if all airports had AWOS or some sort of altimeter setting advisory this incident could have been avoided. Also, there is no substitute for radio communications.

Original NASA ASRS Text

Title: 2 SMAS HAD AN NMAC AT AN UNCONTROLLED ARPT.

Narrative: 10 MI FROM 3B1, UNICOM WAS MONITORED FOR TFC, BUT FROM PRIOR EXPERIENCE OF NO RESPONSE FROM UNICOM, NO CALL WAS MADE FOR TAS. AT ROUGHLY 1 MI FROM ARPT, NORMAL PATTERN WAS ABOUT TO BE ENTERED BY FLYING OVER FIELD TO OBSERVE WINDSOCK. WHILE XING DOWNWIND COURSE FOR RWY 32, NEAR MISS OCCURRED WITH OTHER ACFT IN TFC PATTERN ON DOWNWIND FOR 32. COURSES WERE 90 DEGS TO EACH OTHER AND OTHER ACFT WAS AT TFC PATTERN ALT (2400 MSL) AND OUR ALT WAS APPROX 2600 MSL DSNDING. NO EVASIVE ACTION WAS REQUIRED ALTHOUGH MISS WAS APPROX 50 FT VERT '0' HORIZONTAL. I FEEL CONTRADICTING FACTORS WERE: 1) NEITHER ACFT, ALTHOUGH RADIO EQUIPPED, WERE ANNOUNCING POS. 2) DUE TO SNOW ON GND AND BRIGHT SKIES AND COLOR OF OTHER ACFT BEING PRIMARILY WHITE, TFC WAS NOT EASY TO SEE. 3) WITH NO ALTIMETER SETTING AND DUE TO MY XCOUNTRY, FLT ALT WAS NOT AS THOUGHT. I FEEL THAT IF ALL ARPTS HAD AWOS OR SOME SORT OF ALTIMETER SETTING ADVISORY THIS INCIDENT COULD HAVE BEEN AVOIDED. ALSO, THERE IS NO SUBSTITUTE FOR RADIO COMS.

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.