Narrative:

A near-miss with a landing aircraft occurred at bradford regional airport during takeoff. Wind was calm and there is no preferred runway at bfd. I had taxied to runway 32 and completed my pre-takeoff checklist. After scanning the airport pattern and announcing my intentions to depart the airport to the north on runway 32; I performed my final takeoff checks and took the runway. During rotation; my passenger called out conflicting traffic on runway 23; and I sighted the aircraft slowing and approaching the runway crossing; about 1000 - 2000 feet in front of us. I elected to continue the takeoff instead of trying to brake; and we passed over the aircraft by about 200 feet with about 100 feet horizontal from directly beneath us.after finishing the departure; my passenger and I immediately troubleshooted the situation; verifying that the radio volume was turned up because we had not heard any radio calls from the conflicting aircraft. We found that the radio has been in a lower position; but did not verify the exact level in our haste to ensure radio communication. We did not hear any radio calls post-incident from the conflicting aircraft; but did hear other traffic at bfd later in our flight. It is a distinct possibility that the conflicting aircraft had no radio or did not make position calls; but cannot be said conclusively due to the uncertainty of our radio volume level.after reviewing the situation; I have determined that the root cause was the failure of the crew to ensure that the radio was at an appropriate volume prior to departing the airport. As an environmental contributing factor; it is not possible to see the end of runway 23 from runway 32's hold short line; as well as the end of the downwind; base; and final leg. This is due to high-density; tall trees surrounding the airport. If I or the other pilot had been flying a no-radio aircraft; it would be unlikely that this incident would have been avoided as I would have not seen the landing aircraft.as a pilot; my corrective action is to add squelch checks prior to every departure at an uncontrolled field and build a habit of verifying my radio volume level regularly. I also recommend that it be considered to remove trees near the end of runway 32 to allow proper scanning of the airport pattern on the crossing runway.

Related reports:

Google
 

Original NASA ASRS Text

Title: C172 pilot reported a conflict with another aircraft on takeoff at BFD. Reporter cited poor radio procedures and trees on the airport property as contributing factors.

Narrative: A near-miss with a landing aircraft occurred at Bradford Regional Airport during takeoff. Wind was calm and there is no preferred runway at BFD. I had taxied to Runway 32 and completed my pre-takeoff checklist. After scanning the airport pattern and announcing my intentions to depart the airport to the north on Runway 32; I performed my final takeoff checks and took the runway. During rotation; my passenger called out conflicting traffic on Runway 23; and I sighted the aircraft slowing and approaching the runway crossing; about 1000 - 2000 feet in front of us. I elected to continue the takeoff instead of trying to brake; and we passed over the aircraft by about 200 feet with about 100 feet horizontal from directly beneath us.After finishing the departure; my passenger and I immediately troubleshooted the situation; verifying that the radio volume was turned up because we had not heard any radio calls from the conflicting aircraft. We found that the radio has been in a lower position; but did not verify the exact level in our haste to ensure radio communication. We did not hear any radio calls post-incident from the conflicting aircraft; but did hear other traffic at BFD later in our flight. It is a distinct possibility that the conflicting aircraft had no radio or did not make position calls; but cannot be said conclusively due to the uncertainty of our radio volume level.After reviewing the situation; I have determined that the root cause was the failure of the crew to ensure that the radio was at an appropriate volume prior to departing the airport. As an environmental contributing factor; it is not possible to see the end of Runway 23 from Runway 32's hold short line; as well as the end of the downwind; base; and final leg. This is due to high-density; tall trees surrounding the airport. If I or the other pilot had been flying a no-radio aircraft; it would be unlikely that this incident would have been avoided as I would have not seen the landing aircraft.As a pilot; my corrective action is to add squelch checks prior to every departure at an uncontrolled field and build a habit of verifying my radio volume level regularly. I also recommend that it be considered to remove trees near the end of Runway 32 to allow proper scanning of the airport pattern on the crossing runway.

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.