Narrative:

While taxiing to runway 22 at bhb; we noticed a C-172 holding short of 4-22 at an intersection near the approach end of runway 4. Winds and weather were favoring runway 22 since it is the ILS runway. We continued to make all required radio calls and maintained a listening watch on CTAF during taxi to runway 22. Upon reaching the approach end of runway 22 we finished pre-takeoff checks and cleared the runway visually and via radio. Prior to taxiing onto runway 22 we announced on CTAF that we were taking runway 22 for departure at bhb and heard no response. We taxied onto runway 22 and completed the before takeoff checklist. Just as we were about to power up for takeoff we heard the cessna 172 announce that he was taking runway 4 for departure. We immediately announced that we were in departure position on runway 22 and for the cessna 172 not to takeoff; with no response. The cessna 172 then announced on CTAF that he was taking off on runway 4. We directed him on CTAF to abort his takeoff while we immediately maneuvered off the runway. As we cleared the runway we observed the cessna 172 fly overhead at about 50-100 ft. After the event we took off with no further incident and notified departure of the small aircraft that had taken off on runway 4 with an apparent inability to receive radio communication. In my opinion this event occurred due to two main contributing factors. 1) either the small aircraft had an inoperative radio or the pilot had improperly set up the aircraft's radio; 2) the runway at bhb slopes down from the middle of runway 4-22 towards each of the approach ends thereby preventing pilots at either end from seeing possibly conflicting traffic at the other end of the runway. This situation was noted on the airport diagram page.

Google
 

Original NASA ASRS Text

Title: Two aircraft started their takeoff roll from opposite ends of the same runway at a non-towered airport.

Narrative: While taxiing to Runway 22 at BHB; we noticed a C-172 holding short of 4-22 at an intersection near the approach end of Runway 4. Winds and weather were favoring Runway 22 since it is the ILS runway. We continued to make all required radio calls and maintained a listening watch on CTAF during taxi to Runway 22. Upon reaching the approach end of Runway 22 we finished pre-takeoff checks and cleared the runway visually and via radio. Prior to taxiing onto Runway 22 we announced on CTAF that we were taking Runway 22 for departure at BHB and heard no response. We taxied onto Runway 22 and completed the Before Takeoff checklist. Just as we were about to power up for takeoff we heard the Cessna 172 announce that he was taking Runway 4 for departure. We immediately announced that we were in departure position on Runway 22 and for the Cessna 172 not to takeoff; with no response. The Cessna 172 then announced on CTAF that he was taking off on Runway 4. We directed him on CTAF to abort his takeoff while we immediately maneuvered off the runway. As we cleared the runway we observed the Cessna 172 fly overhead at about 50-100 FT. After the event we took off with no further incident and notified Departure of the small aircraft that had taken off on Runway 4 with an apparent inability to receive radio communication. In my opinion this event occurred due to two main contributing factors. 1) Either the small aircraft had an inoperative radio or the pilot had improperly set up the aircraft's radio; 2) The runway at BHB slopes down from the middle of Runway 4-22 towards each of the approach ends thereby preventing pilots at either end from seeing possibly conflicting traffic at the other end of the runway. This situation was noted on the airport diagram page.

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