Narrative:

After a 1 1/2 hour delay at avl in the early morning, I asked local controller what the visibility was for a runway 16 takeoff. He responded that RVV values for runway 34 were guiding for runway 34 takeoff and runway 16 was prevailing visibility. Takeoff minimums for runways 16/34 were 1/4 mi, however at the departure end of runway 16 visibility was at least 1/4 mi. Tower was calling the visibility 1/8 and rapidly improving. We departed avl with normal takeoff conditions. Upon further research it appears that a pilot with 20 yrs experience does not have the authority/authorized to make a WX judgement at this time and the tower visibility of 1/8 mi was controling. I was, however, told by the local controller that if I was comfortable with the visibility as I called it that I could depart.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF AN MLG TKOF BELOW REQUIRED MINIMUMS.

Narrative: AFTER A 1 1/2 HR DELAY AT AVL IN THE EARLY MORNING, I ASKED LCL CTLR WHAT THE VISIBILITY WAS FOR A RWY 16 TKOF. HE RESPONDED THAT RVV VALUES FOR RWY 34 WERE GUIDING FOR RWY 34 TKOF AND RWY 16 WAS PREVAILING VISIBILITY. TKOF MINIMUMS FOR RWYS 16/34 WERE 1/4 MI, HOWEVER AT THE DEP END OF RWY 16 VISIBILITY WAS AT LEAST 1/4 MI. TWR WAS CALLING THE VISIBILITY 1/8 AND RAPIDLY IMPROVING. WE DEPARTED AVL WITH NORMAL TKOF CONDITIONS. UPON FURTHER RESEARCH IT APPEARS THAT A PLT WITH 20 YRS EXPERIENCE DOES NOT HAVE THE AUTH TO MAKE A WX JUDGEMENT AT THIS TIME AND THE TWR VISIBILITY OF 1/8 MI WAS CTLING. I WAS, HOWEVER, TOLD BY THE LCL CTLR THAT IF I WAS COMFORTABLE WITH THE VISIBILITY AS I CALLED IT THAT I COULD DEPART.

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.