Narrative:

I replaced a new captain on high limits in order to operate a diverted flight back to cle. Cle had snow, fog, partially obscured, sky with RVR between 3000 and 3500' all morning. When the diverted flight arrived at the gate in pit, plans were quickly made to meet my crew in phx later in the day to rejoin my normal trip sequence and I boarded the flight. The jetway was pulled quickly and we taxied out. My first officer left the flight plan with the gate agent, the agent who closed the flight out said paperwork would come on the ACARS. Taxiing out was uneventful and we had several small traffic delays taxiing out. We called the station and advised load planning that we did not have the weight and balance data in the ACARS yet and we were approaching the runway for takeoff. We repeatedly touched and prompted the ACARS touch screen to activate the weight and balance page and continually received a south/B data not available message as we taxied in line for takeoff. Load planning was manually computing the data since the diverted flight was a non standard operation for load planning. As we became #1 for takeoff, just prior to the tower's 'position and hold' call, we touched west/B command again and data filled the screen. We acknowledged our takeoff clearance, set our takeoff speeds and charts and took off. Upon reaching phx, 2 legs and over 5 hours later, the chief pilot's office from the phl crew base called to report that flight had departed pit-cle west/O takeoff data and that the load planning office in pit had called the FAA regional office to report same. I think I had exerted a lot of pressure on load planning to hurry the data. Why I received data on my touch screen and then had it reported that there was no data to the FAA leads me to assume an irritated employee is trying to make trouble for me. Unfortunately, I have no hard copy records of my weight data and must rely on company records, probably fabricated by the disgruntled employee trying to implicate me in illegal activity.

Google
 

Original NASA ASRS Text

Title: ALLEGED TKOF WITHOUT WEIGHT AND BALANCE DATA.

Narrative: I REPLACED A NEW CAPT ON HIGH LIMITS IN ORDER TO OPERATE A DIVERTED FLT BACK TO CLE. CLE HAD SNOW, FOG, PARTIALLY OBSCURED, SKY WITH RVR BTWN 3000 AND 3500' ALL MORNING. WHEN THE DIVERTED FLT ARRIVED AT THE GATE IN PIT, PLANS WERE QUICKLY MADE TO MEET MY CREW IN PHX LATER IN THE DAY TO REJOIN MY NORMAL TRIP SEQUENCE AND I BOARDED THE FLT. THE JETWAY WAS PULLED QUICKLY AND WE TAXIED OUT. MY F/O LEFT THE FLT PLAN WITH THE GATE AGENT, THE AGENT WHO CLOSED THE FLT OUT SAID PAPERWORK WOULD COME ON THE ACARS. TAXIING OUT WAS UNEVENTFUL AND WE HAD SEVERAL SMALL TFC DELAYS TAXIING OUT. WE CALLED THE STATION AND ADVISED LOAD PLANNING THAT WE DID NOT HAVE THE WT AND BAL DATA IN THE ACARS YET AND WE WERE APCHING THE RWY FOR TKOF. WE REPEATEDLY TOUCHED AND PROMPTED THE ACARS TOUCH SCREEN TO ACTIVATE THE WT AND BAL PAGE AND CONTINUALLY RECEIVED A S/B DATA NOT AVAILABLE MESSAGE AS WE TAXIED IN LINE FOR TKOF. LOAD PLANNING WAS MANUALLY COMPUTING THE DATA SINCE THE DIVERTED FLT WAS A NON STANDARD OPERATION FOR LOAD PLANNING. AS WE BECAME #1 FOR TKOF, JUST PRIOR TO THE TWR'S 'POS AND HOLD' CALL, WE TOUCHED W/B COMMAND AGAIN AND DATA FILLED THE SCREEN. WE ACKNOWLEDGED OUR TKOF CLRNC, SET OUR TKOF SPDS AND CHARTS AND TOOK OFF. UPON REACHING PHX, 2 LEGS AND OVER 5 HRS LATER, THE CHIEF PLT'S OFFICE FROM THE PHL CREW BASE CALLED TO RPT THAT FLT HAD DEPARTED PIT-CLE W/O TKOF DATA AND THAT THE LOAD PLANNING OFFICE IN PIT HAD CALLED THE FAA REGIONAL OFFICE TO RPT SAME. I THINK I HAD EXERTED A LOT OF PRESSURE ON LOAD PLANNING TO HURRY THE DATA. WHY I RECEIVED DATA ON MY TOUCH SCREEN AND THEN HAD IT RPTED THAT THERE WAS NO DATA TO THE FAA LEADS ME TO ASSUME AN IRRITATED EMPLOYEE IS TRYING TO MAKE TROUBLE FOR ME. UNFORTUNATELY, I HAVE NO HARD COPY RECORDS OF MY WT DATA AND MUST RELY ON COMPANY RECORDS, PROBABLY FABRICATED BY THE DISGRUNTLED EMPLOYEE TRYING TO IMPLICATE ME IN ILLEGAL ACTIVITY.

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