Takeoff below minimum RVR.

Attributes
ACN	295942
Time
Date	199502
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mco
State Reference	FL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	climbout : takeoff
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : instrument pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 240 flight time total : 19000 flight time type : 1000
ASRS Report	295942
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Experience	flight time last 90 days : 100 flight time total : 7800
ASRS Report	295174
Events
Anomaly	non adherence : published procedure non adherence : far other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While taxiing out for takeoff at mco runway visibility was reported as 6, 6, and 6 several times. When #1 for takeoff, tower reported RVR less than 600 ft can you go? We misunderstood tower, still having a 600 ft RVR mindset, and replied yes. We were cleared for takeoff. During takeoff roll we heard tower talking to other airline aircraft and realized that the tower had probably reported the RVR at less than 600 ft and we actually were not legal for takeoff. I considered it safer to continue the takeoff, rather than make a high speed abort in the fog. Takeoff was normal, and we continued on to iah. Supplemental information from acn 295174: after our takeoff roll had been initiated, tower contacted the next aircraft in line for takeoff (another airline flight) and advised them that RVR for runway 36R was less than 600 ft, could they accept a takeoff. The other airline responded that they needed 600 ft RVR and, therefore, could not takeoff. After takeoff, I questioned if tower had also given us less than 600 ft RVR, but this information was misinterpreted due to completion of the before takeoff checklist. No unusual or dangerous situation resulted from the decision to continue the takeoff.

Original NASA ASRS Text

Title: TKOF BELOW MINIMUM RVR.

Narrative: WHILE TAXIING OUT FOR TKOF AT MCO RWY VISIBILITY WAS RPTED AS 6, 6, AND 6 SEVERAL TIMES. WHEN #1 FOR TKOF, TWR RPTED RVR LESS THAN 600 FT CAN YOU GO? WE MISUNDERSTOOD TWR, STILL HAVING A 600 FT RVR MINDSET, AND REPLIED YES. WE WERE CLRED FOR TKOF. DURING TKOF ROLL WE HEARD TWR TALKING TO OTHER AIRLINE ACFT AND REALIZED THAT THE TWR HAD PROBABLY RPTED THE RVR AT LESS THAN 600 FT AND WE ACTUALLY WERE NOT LEGAL FOR TKOF. I CONSIDERED IT SAFER TO CONTINUE THE TKOF, RATHER THAN MAKE A HIGH SPD ABORT IN THE FOG. TKOF WAS NORMAL, AND WE CONTINUED ON TO IAH. SUPPLEMENTAL INFO FROM ACN 295174: AFTER OUR TKOF ROLL HAD BEEN INITIATED, TWR CONTACTED THE NEXT ACFT IN LINE FOR TKOF (ANOTHER AIRLINE FLT) AND ADVISED THEM THAT RVR FOR RWY 36R WAS LESS THAN 600 FT, COULD THEY ACCEPT A TKOF. THE OTHER AIRLINE RESPONDED THAT THEY NEEDED 600 FT RVR AND, THEREFORE, COULD NOT TKOF. AFTER TKOF, I QUESTIONED IF TWR HAD ALSO GIVEN US LESS THAN 600 FT RVR, BUT THIS INFO WAS MISINTERPRETED DUE TO COMPLETION OF THE BEFORE TKOF CHKLIST. NO UNUSUAL OR DANGEROUS SIT RESULTED FROM THE DECISION TO CONTINUE THE TKOF.

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.