Narrative:

Upon leaving ramp for a runway 26 departure we heard a piper cub request landing on runway 8. It was a dark night; with layered clouds; and light rain or mist obstructing visibility. We could see the beacon of the cub about 2 miles south of runway 26. Tower controller advised cub of a delay due to departing 26 traffic unless cub could accept 26 which pilot declined. We commented on how the new procedures in jnu compromised safety in this instance. The cub could have landed; parked; and left the airport in the 4 to 5 minutes it took us to taxi and be ready at runway 26. Instead; the cub held on a dark night in mountainous terrain. We reached the end and we were cleared for takeoff. We could not locate the cub and requested his position before commencing takeoff roll. The controller could not see the cub; but was informed the cub was over the 'brotherton' bridge and we were told about a mile north of the runway. We departed and started an early turn for the barlo departure. Passing about 600 feet the first officer advised that it was a good thing we turned early because the cub was about 200 feet below us and directly off our right wing. What appears to be a silly procedure from our prospective hindered the controller from using his discretion to land an aircraft during the time we taxied for departure. Instead; the aircraft held and then almost created a conflict with out departure. The next time this situation happens I will not takeoff until we can visually see the other aircraft or tower allows the aircraft to land. This night safety was not increased.[the event was caused by] poor procedures for runway usage. Not allowing ATC to use its judgment and training to separate traffic.

Related reports:

Google
 

Original NASA ASRS Text

Title: The Captain of a night time commercial departure from JNU reported a conflict with an inbound Piper 'Cub.' A new airport procedure specifying coordination of opposite direction; concurrent arrivals and departures at night was cited as a contributing factor.

Narrative: Upon leaving ramp for a runway 26 departure we heard a Piper Cub request landing on runway 8. It was a dark night; with layered clouds; and light rain or mist obstructing visibility. We could see the beacon of the cub about 2 miles south of runway 26. Tower controller advised Cub of a delay due to departing 26 traffic unless Cub could accept 26 which pilot declined. We commented on how the new procedures in JNU compromised safety in this instance. The Cub could have landed; parked; and left the airport in the 4 to 5 minutes it took us to taxi and be ready at runway 26. Instead; the Cub held on a dark night in mountainous terrain. We reached the end and we were cleared for takeoff. We could not locate the Cub and requested his position before commencing takeoff roll. The controller could not see the Cub; but was informed the Cub was over the 'Brotherton' bridge and we were told about a mile north of the runway. We departed and started an early turn for the Barlo Departure. Passing about 600 feet the F/O advised that it was a good thing we turned early because the Cub was about 200 feet below us and directly off our right wing. What appears to be a silly procedure from our prospective hindered the controller from using his discretion to land an aircraft during the time we taxied for departure. Instead; the aircraft held and then almost created a conflict with out departure. The next time this situation happens I will not takeoff until we can visually see the other aircraft or tower allows the aircraft to land. This night safety was not increased.[The event was caused by] poor procedures for runway usage. Not allowing ATC to use its judgment and training to separate traffic.

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.