Narrative:

En route from orf to iad I was rerouted to rdu by our dispatch for scheduling reasons. After turning towards rdu and committing myself, I asked for the fuel burn, min fuel, etc, from dispatch. This took a while to figure. My first officer and I then discussed the situation. I then went back to the radio to double check the WX in rdu. There wasn't a cloud in sight at our present position so I assumed rdu would be VFR. My dispatcher came back, after another delay, and told me that rdu had 2.5 mi visibility. I did not have enough fuel for an alternate at this point and rdu was my closest usable airport. I felt I had already committed myself too far and needed to continue to rdu. We continued, shot the ILS and landed uneventfully. Contributing factors included the lack of rdu WX in my WX package since it was not our original destination, delays experienced in communicating over 'atlanta radio' to my dispatcher, afis system being unable to pull up WX forcing me to use a radio link to dispatch and fatigue. This was day 3 of a three day trip. The night before I went to sleep at approximately XA00 am. At XF00 am I was woken up by scheduling asking if I could go to the airport to deal with a maintenance issue. I did have my legal rest amount but not much sleep. The flight was a repo flight operated under part 91. I do not know what the forecast at rdu was during this flight, only the current conditions.

Related reports:

Google
 

Original NASA ASRS Text

Title: BAE 4100 FLC WERE DIVERTED BY DISPATCHER TO ANOTHER ARPT DURING CRUISE FOR SCHEDULING PURPOSES WITHOUT SUFFICIENT FUEL REMAINING FOR A REQUIRED ALTERNATE.

Narrative: ENRTE FROM ORF TO IAD I WAS REROUTED TO RDU BY OUR DISPATCH FOR SCHEDULING REASONS. AFTER TURNING TOWARDS RDU AND COMMITTING MYSELF, I ASKED FOR THE FUEL BURN, MIN FUEL, ETC, FROM DISPATCH. THIS TOOK A WHILE TO FIGURE. MY FO AND I THEN DISCUSSED THE SIT. I THEN WENT BACK TO THE RADIO TO DOUBLE CHK THE WX IN RDU. THERE WASN'T A CLOUD IN SIGHT AT OUR PRESENT POS SO I ASSUMED RDU WOULD BE VFR. MY DISPATCHER CAME BACK, AFTER ANOTHER DELAY, AND TOLD ME THAT RDU HAD 2.5 MI VISIBILITY. I DID NOT HAVE ENOUGH FUEL FOR AN ALTERNATE AT THIS POINT AND RDU WAS MY CLOSEST USABLE ARPT. I FELT I HAD ALREADY COMMITTED MYSELF TOO FAR AND NEEDED TO CONTINUE TO RDU. WE CONTINUED, SHOT THE ILS AND LANDED UNEVENTFULLY. CONTRIBUTING FACTORS INCLUDED THE LACK OF RDU WX IN MY WX PACKAGE SINCE IT WAS NOT OUR ORIGINAL DESTINATION, DELAYS EXPERIENCED IN COMMUNICATING OVER 'ATLANTA RADIO' TO MY DISPATCHER, AFIS SYS BEING UNABLE TO PULL UP WX FORCING ME TO USE A RADIO LINK TO DISPATCH AND FATIGUE. THIS WAS DAY 3 OF A THREE DAY TRIP. THE NIGHT BEFORE I WENT TO SLEEP AT APPROX XA00 AM. AT XF00 AM I WAS WOKEN UP BY SCHEDULING ASKING IF I COULD GO TO THE ARPT TO DEAL WITH A MAINT ISSUE. I DID HAVE MY LEGAL REST AMOUNT BUT NOT MUCH SLEEP. THE FLT WAS A REPO FLT OPERATED UNDER PART 91. I DO NOT KNOW WHAT THE FORECAST AT RDU WAS DURING THIS FLT, ONLY THE CURRENT CONDITIONS.

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.