An air carrier intersection takeoff without proper performance data available.

Attributes
ACN	544075
Time
Date	200204
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : cvg.airport
State Reference	OH
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Regional Jet CL65, Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : multi engine pilot : cfi pilot : instrument
Experience	flight time last 90 days : 250 flight time total : 3000 flight time type : 1600
ASRS Report	544075
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 16000 flight time type : 5000
ASRS Report	544074
Events
Anomaly	non adherence : far non adherence : published procedure non adherence : company policies
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Taxi instruction received with 'hold short for release.' single engine taxi (normal operations). Ground instructed us to prepare for an immediate takeoff, assigned a rerte, and instructed us to call tower and look for emergency vehicles. We ran checklists (engine start, pre takeoff, line-up) and contacted tower. He asked if an intersection departure was possible from taxiway K4 on runway 27 (cvg). We replied 'affirmative.' supplemental information from acn 544074: captain stated we would use normal thrust rather than reduced. After takeoff and through 10000 ft, we realized that the data for a taxiway K4 departure was no longer in runway analysis. Takeoff and departure were uneventful and safe. I, as captain, allowed myself and crew to get overloaded and rushed. Also went by 'memory' that we had used taxiway K4 in past when runway was partially closed. While takeoff was safely completed and necessary obstruction clearance, etc probably existed, we could have taken the extra 20 seconds to confirm data, but didn't. We allowed on-time performance to rule the decisions.

Original NASA ASRS Text

Title: AN ACR INTXN TKOF WITHOUT PROPER PERFORMANCE DATA AVAILABLE.

Narrative: TAXI INSTRUCTION RECEIVED WITH 'HOLD SHORT FOR RELEASE.' SINGLE ENG TAXI (NORMAL OPS). GND INSTRUCTED US TO PREPARE FOR AN IMMEDIATE TKOF, ASSIGNED A RERTE, AND INSTRUCTED US TO CALL TWR AND LOOK FOR EMER VEHICLES. WE RAN CHKLISTS (ENG START, PRE TKOF, LINE-UP) AND CONTACTED TWR. HE ASKED IF AN INTXN DEP WAS POSSIBLE FROM TXWY K4 ON RWY 27 (CVG). WE REPLIED 'AFFIRMATIVE.' SUPPLEMENTAL INFO FROM ACN 544074: CAPT STATED WE WOULD USE NORMAL THRUST RATHER THAN REDUCED. AFTER TKOF AND THROUGH 10000 FT, WE REALIZED THAT THE DATA FOR A TXWY K4 DEP WAS NO LONGER IN RWY ANALYSIS. TKOF AND DEP WERE UNEVENTFUL AND SAFE. I, AS CAPT, ALLOWED MYSELF AND CREW TO GET OVERLOADED AND RUSHED. ALSO WENT BY 'MEMORY' THAT WE HAD USED TXWY K4 IN PAST WHEN RWY WAS PARTIALLY CLOSED. WHILE TKOF WAS SAFELY COMPLETED AND NECESSARY OBSTRUCTION CLRNC, ETC PROBABLY EXISTED, WE COULD HAVE TAKEN THE EXTRA 20 SECONDS TO CONFIRM DATA, BUT DIDN'T. WE ALLOWED ON-TIME PERFORMANCE TO RULE THE DECISIONS.

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.