B737 captain is instructed to taxi to runway 4 at hou via K and K1; then cleared for takeoff on runw...

Narrative:

Aircraft cleared to taxi to runway 4 at hou via taxiway K; K1. K1 taxiway bisects runway 4 & runway 35. Tower cleared aircraft for immediate takeoff on runway 4 at intersection K1. The heading bug was selected to runway 4 on both pfd's. PF lined up incorrectly on runway 35 and momentarily advanced power levers. As aircraft reached taxi speed PNF announced discontinue takeoff; not lined up on runway 4. Aircraft had already rolled through the runway 4 boundary and tower was advised we were discontinuing takeoff. Tower advised no problem and reassigned runway 12R for departure. Lead flight attendant was summoned to the cockpit and advised. Aircraft had landed on runway 12R. FMC was subsequently set up on the ramp for takeoff on runway 12R. Upon taxi out; tower assigned runway 4 at intersection K1 for departure. PNF made the changes in the FMS as needed and verbally briefed PF during taxi. In the future; PF will take time prior to takeoff to stop the aircraft and visually review charts; etc. For situational awareness. Also; I recommended the company B737 line up checklist be amended to resemble our other checklists to include; 'takeoff runway/heading....verified;' as the last item. It should be noted that K1 intersection at hou is beyond the painted runway markings for both runway 4 & 35. Also; runway signage at this intersection is not illuminated. A suggestion to the commercial chart maker is being made to update the airport diagram to include a hotspot notation to alert pilots to be extra vigilant when cleared for takeoff at night from the K1 intersection. Finally; familiarity breeds complacency. Although I have not flown into hou for over a year; having previously flight instructed there; in my early career; contributed to my being less vigilant and alert as I must always be.

Original NASA ASRS Text

Title: B737 Captain is instructed to taxi to Runway 4 at HOU via K and K1; then cleared for takeoff on Runway 4. Reporter lines up on Runway 35 and begins takeoff before PNF notices the error and informs the PF. A lack of signage and darkness were cited as contributing factors.

Narrative: Aircraft cleared to taxi to Runway 4 at HOU via Taxiway K; K1. K1 Taxiway bisects Runway 4 & Runway 35. Tower cleared aircraft for immediate takeoff on Runway 4 at intersection K1. The heading bug was selected to Runway 4 on both PFD's. PF lined up incorrectly on Runway 35 and momentarily advanced power levers. As aircraft reached taxi speed PNF announced discontinue takeoff; not lined up on Runway 4. Aircraft had already rolled through the Runway 4 boundary and Tower was advised we were discontinuing takeoff. Tower advised no problem and reassigned Runway 12R for departure. Lead flight attendant was summoned to the cockpit and advised. Aircraft had landed on Runway 12R. FMC was subsequently set up on the ramp for takeoff on Runway 12R. Upon taxi out; Tower assigned Runway 4 at intersection K1 for departure. PNF made the changes in the FMS as needed and verbally briefed PF during taxi. In the future; PF will take time prior to takeoff to stop the aircraft and visually review charts; etc. for situational awareness. Also; I recommended the company B737 Line Up Checklist be amended to resemble our other checklists to include; 'Takeoff Runway/Heading....Verified;' as the last item. It should be noted that K1 intersection at HOU is beyond the painted runway markings for both Runway 4 & 35. Also; runway signage at this intersection is not illuminated. A suggestion to the Commercial chart maker is being made to update the airport diagram to include a HOTSPOT notation to alert pilots to be extra vigilant when cleared for takeoff at night from the K1 intersection. Finally; familiarity breeds complacency. Although I have not flown into HOU for over a year; having previously flight instructed there; in my early career; contributed to my being less vigilant and alert as I must always be.

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

Attributes
ACN	976348
Time
Date	201110
Local Time Of Day	1801-2400
Place
Locale Reference	HOU.Tower
State Reference	TX
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	B737 Next Generation Undifferentiated
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Route In Use	None
Flight Plan	IFR
Person 1
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument
Experience	Flight Crew Last 90 Days 100 Flight Crew Total 14000 Flight Crew Type 3500
Events
Anomaly	Deviation - Procedural Clearance Ground Incursion Runway

B737 captain is instructed to taxi to runway 4 at hou via K and K1; then cleared for takeoff on runway 4. Reporter lines up on runway 35 and begins takeoff before PNF notices the error and informs the PF. A lack of signage and darkness were cited as contributing factors.