The reporter took off from uncontrolled airport not aware of traffic landing on crossing runway.

Attributes
ACN	275847
Time
Date	199406
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mtj
State Reference	CO
Altitude	agl bound lower : 0 agl bound upper : 1000
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	other : unknown
Flight Phase	climbout : takeoff
Flight Plan	VFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	other : unknown
Flight Phase	landing other
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : instrument pilot : private
Experience	flight time last 90 days : 20 flight time total : 800 flight time type : 300
ASRS Report	275847
Person 2
Affiliation	Other
Function	flight crew : single pilot
Events
Anomaly	conflict : ground critical conflict : nmac other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	horizontal : 1000 vertical : 1000
Supplementary
Primary Problem	Flight Crew Human Performance

Narrative:

Uneventful preflight, taxi and run up. Run-up was done at northwest end of runway 17. I announced all my intentions -- taxi, entry onto runway 17 for departure. As I departed and crossed over runway 31 I saw a twin crossing the numbers and landing on runway 31. I was past runway 31 before he crossed under me. It scared me to think of the potential problems which could've arisen -- a go around by the other traffic, etc. Our airport is uncontrolled, no radio contact is necessary. I never heard him announce so I wonder if he called in while I was doing my run-up. The engine noise and maybe a radio turned down could have caused me not to hear him or he never announced. It would be very difficult for me to spot him on base or final to 31 from the end of runway 17. Solutions are only partial -- call unicom to see if there's traffic I haven't heard, keep radios loud during run-up, be ready to abort if unexpected traffic is spotted. (If landing traffic doesn't announce then unicom can't help me). Once again, communication is critical, but doesn't replace see and be seen.

Original NASA ASRS Text

Title: THE RPTR TOOK OFF FROM UNCTLED ARPT NOT AWARE OF TFC LNDG ON XING RWY.

Narrative: UNEVENTFUL PREFLT, TAXI AND RUN UP. RUN-UP WAS DONE AT NW END OF RWY 17. I ANNOUNCED ALL MY INTENTIONS -- TAXI, ENTRY ONTO RWY 17 FOR DEP. AS I DEPARTED AND CROSSED OVER RWY 31 I SAW A TWIN XING THE NUMBERS AND LNDG ON RWY 31. I WAS PAST RWY 31 BEFORE HE CROSSED UNDER ME. IT SCARED ME TO THINK OF THE POTENTIAL PROBS WHICH COULD'VE ARISEN -- A GAR BY THE OTHER TFC, ETC. OUR ARPT IS UNCTLED, NO RADIO CONTACT IS NECESSARY. I NEVER HEARD HIM ANNOUNCE SO I WONDER IF HE CALLED IN WHILE I WAS DOING MY RUN-UP. THE ENG NOISE AND MAYBE A RADIO TURNED DOWN COULD HAVE CAUSED ME NOT TO HEAR HIM OR HE NEVER ANNOUNCED. IT WOULD BE VERY DIFFICULT FOR ME TO SPOT HIM ON BASE OR FINAL TO 31 FROM THE END OF RWY 17. SOLUTIONS ARE ONLY PARTIAL -- CALL UNICOM TO SEE IF THERE'S TFC I HAVEN'T HEARD, KEEP RADIOS LOUD DURING RUN-UP, BE READY TO ABORT IF UNEXPECTED TFC IS SPOTTED. (IF LNDG TFC DOESN'T ANNOUNCE THEN UNICOM CAN'T HELP ME). ONCE AGAIN, COM IS CRITICAL, BUT DOESN'T REPLACE SEE AND BE SEEN.

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.