Narrative:

Departed U64 runway 16 with a left crosswind departure heading 210 to vortac tbc and was communicating and monitoring 122.8 at approximately 8;200 feet MSL; half way between bdg and U64; climbing to my cruise altitude of 10500. To the best of my very short glimpse; a white cessna in the 172 to 210 class passed under us at my estimate of less than 50 no more than 75 feet. I estimate the other aircraft's heading to be 020 to 040. Very close! I didn't have time to react or take evasive action. I was with one passenger who was not viewing out the window; until the last minute and was freaked! I didn't see the aircraft either until a -second after my passenger. I was trimming the aircraft; using 122.8 the unicom tower frequencies for both mountains to the right of us and no communications on 122.8; and at that altitude the closest center is denver would not be able to track you and I don't think that there is radio communication possible either from denver at that altitude. I assumed that with the mountains covering most of the right side of flight no aircraft flying from the left side directly to the mountains and no aircraft using 122.8 in the area that I was in a safe zone and could monitor the instruments and continue to trim the aircraft. The aircraft in the area and at and below the mountain range height of 11;200 would or should be on 122.8. I believe what caused the problem was the other aircrafts lack of communication on 122.8 in the close proximity of the two airports either giving or asking for traffic advisory? It is very difficult I have been told to see an aircraft heading directly at you? If I could talk to the other pilot I would ask him; why he was not on 122.8 asking for traffic advisories; at that altitude? Me I will instruct any of my passengers; (more than once); to help me scan the area and keep an eye out for other aircraft! Making it part of my check list!

Related reports:

Google
 

Original NASA ASRS Text

Title: BE33 pilot climbing out of U64 experiences a NMAC with a Cessna at 8200 feet flying in the opposite direction. The Cessna was not detected in time to take any evasive action.

Narrative: Departed U64 runway 16 with a left crosswind departure heading 210 to vortac TBC and was communicating and monitoring 122.8 at approximately 8;200 feet MSL; half way between BDG and U64; climbing to my cruise altitude of 10500. To the best of my very short glimpse; a white Cessna in the 172 to 210 class passed under us at my estimate of less than 50 no more than 75 feet. I estimate the other aircraft's heading to be 020 to 040. VERY CLOSE! I didn't have time to react or take evasive action. I was with one passenger who was not viewing out the window; until the last minute and was FREAKED! I didn't see the aircraft either until a -second after my passenger. I was trimming the aircraft; using 122.8 the Unicom tower frequencies for both mountains to the right of us and no communications on 122.8; and at that altitude the closest center is Denver would not be able to track you and I don't think that there is radio communication possible either from Denver at that altitude. I assumed that with the mountains covering most of the right side of flight no aircraft flying from the left side directly to the mountains and no aircraft using 122.8 in the area that I was in a safe zone and could monitor the instruments and continue to trim the aircraft. The aircraft in the area and at and below the mountain range height of 11;200 would or should be on 122.8. I believe what caused the problem was the other aircrafts lack of communication on 122.8 in the close proximity of the two airports either giving or asking for traffic advisory? It is very difficult I have been told to see an aircraft heading directly at you? If I could talk to the other pilot I would ask him; why he was not on 122.8 asking for traffic advisories; at that altitude? Me I will instruct any of my passengers; (more than once); to help me scan the area and keep an eye out for other aircraft! Making it part of my check list!

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