Takeoff performance data not available for runway used for takeoff. Discovered after the fact.

Attributes
ACN	468550
Time
Date	200003
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sea.airport
State Reference	WA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : sea.tower tower : mem.tower
Operator	common carrier : air carrier
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : takeoff ground : takeoff roll
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : cfi pilot : atp
Experience	flight time last 90 days : 50 flight time total : 5700 flight time type : 50
ASRS Report	468550
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : multi engine pilot : instrument
Events
Anomaly	non adherence : far non adherence : company policies other anomaly other
Independent Detector	other flight crewb
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance Company
Primary Problem	Flight Crew Human Performance

Narrative:

Told to taxi runway 16L at lima intersection for takeoff. Tower clears us to cross runway 16L at taxiway J hold short runway 16R. Next we are cleared to take off runway 16R at taxiway J. Upon later discussion, the first officer tells me we don't have takeoff data for a taxiway J intersection departure on the right runway. She mistook the data for runway 16L as runway 16R data. Factors leading to the problem: 1) I am a new captain with low experience (hi minimums). 2) there is so much runway available, I did not even think to check for ATOG's from that intersection. In the future I need to be more careful when given a non standard clearance, and rechk ATOG's when given a different intersection. Safety was definitely not an issue due to the amount of runway available but the fact still remains that the company does not give us data for takeoff from that intersection. This was an inadvertent illegal departure.

Original NASA ASRS Text

Title: TKOF PERFORMANCE DATA NOT AVAILABLE FOR RWY USED FOR TKOF. DISCOVERED AFTER THE FACT.

Narrative: TOLD TO TAXI RWY 16L AT LIMA INTXN FOR TKOF. TWR CLRS US TO CROSS RWY 16L AT TXWY J HOLD SHORT RWY 16R. NEXT WE ARE CLRED TO TAKE OFF RWY 16R AT TXWY J. UPON LATER DISCUSSION, THE FO TELLS ME WE DON'T HAVE TKOF DATA FOR A TXWY J INTXN DEP ON THE R RWY. SHE MISTOOK THE DATA FOR RWY 16L AS RWY 16R DATA. FACTORS LEADING TO THE PROB: 1) I AM A NEW CAPT WITH LOW EXPERIENCE (HI MINIMUMS). 2) THERE IS SO MUCH RWY AVAILABLE, I DID NOT EVEN THINK TO CHK FOR ATOG'S FROM THAT INTXN. IN THE FUTURE I NEED TO BE MORE CAREFUL WHEN GIVEN A NON STANDARD CLRNC, AND RECHK ATOG'S WHEN GIVEN A DIFFERENT INTXN. SAFETY WAS DEFINITELY NOT AN ISSUE DUE TO THE AMOUNT OF RWY AVAILABLE BUT THE FACT STILL REMAINS THAT THE COMPANY DOES NOT GIVE US DATA FOR TKOF FROM THAT INTXN. THIS WAS AN INADVERTENT ILLEGAL DEP.

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.