Runway incursion, runway 35, during a night operation at mem, tn.

Attributes
ACN	541764
Time
Date	200203
Day	Fri
Local Time Of Day	0001 To 0600
Place
Locale Reference	airport : mem.airport
State Reference	TN
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-11
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : holding
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 30 flight time total : 11000 flight time type : 1500
ASRS Report	541764
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 3500 flight time type : 240
ASRS Report	542173
Events
Anomaly	incursion : runway non adherence : published procedure non adherence : company policies non adherence : clearance non adherence : far other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor Company Chart Or Publication ATC Human Performance Airport
Primary Problem	Airport
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : mem.comrdo
Airport	construction : mem.airport lighting : mem.airport markings : mem.airport procedure or policy : mem.airport signage : mem.airport

Narrative:

Runway/taxiway construction mem, taxiway M, changed to runway 35. New procedures in effect shown on 10-8 yellow pages. Company literature very unspecific as to where the holding point for runway 35 is. The information can be found on the back of 10-8, but spot is hard to find in dark. This was my crew's first departure runway 35 and we held short of runway 35 behind departing traffic. Tower questioned us as to if we were at spot N1, and we replied we were holding short of runway 35. Spot N1 (where we were supposed to hold) was actually behind us. The 10-8 chart could be more clear. Also, the company literature and photograph of runway 35 were produced earlier in the construction phase and no mention of the new hold short or N1 spot is made. The photo of taxiway north and runway 35 was taken before the hold short markings were painted. My first early morning departure and I had just arrived from oak may have contributed to missing the note on the 10-8.

Original NASA ASRS Text

Title: RWY INCURSION, RWY 35, DURING A NIGHT OP AT MEM, TN.

Narrative: RWY/TXWY CONSTRUCTION MEM, TXWY M, CHANGED TO RWY 35. NEW PROCS IN EFFECT SHOWN ON 10-8 YELLOW PAGES. COMPANY LITERATURE VERY UNSPECIFIC AS TO WHERE THE HOLDING POINT FOR RWY 35 IS. THE INFO CAN BE FOUND ON THE BACK OF 10-8, BUT SPOT IS HARD TO FIND IN DARK. THIS WAS MY CREW'S FIRST DEP RWY 35 AND WE HELD SHORT OF RWY 35 BEHIND DEPARTING TFC. TWR QUESTIONED US AS TO IF WE WERE AT SPOT N1, AND WE REPLIED WE WERE HOLDING SHORT OF RWY 35. SPOT N1 (WHERE WE WERE SUPPOSED TO HOLD) WAS ACTUALLY BEHIND US. THE 10-8 CHART COULD BE MORE CLR. ALSO, THE COMPANY LITERATURE AND PHOTOGRAPH OF RWY 35 WERE PRODUCED EARLIER IN THE CONSTRUCTION PHASE AND NO MENTION OF THE NEW HOLD SHORT OR N1 SPOT IS MADE. THE PHOTO OF TXWY N AND RWY 35 WAS TAKEN BEFORE THE HOLD SHORT MARKINGS WERE PAINTED. MY FIRST EARLY MORNING DEP AND I HAD JUST ARRIVED FROM OAK MAY HAVE CONTRIBUTED TO MISSING THE NOTE ON THE 10-8.

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.