Runway incursion when the flight crew of a B737-400 landing without clearance, off frequency from th...

Attributes
ACN	556786
Time
Date	200208
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sea.airport
State Reference	WA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : s46.tracon tower : sea.tower tower : lax.tower
Operator	common carrier : air carrier
Make Model Name	B737-400
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : visual
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : s46.tracon tower : sea.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 240 flight time total : 10000 flight time type : 1500
ASRS Report	556786
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	incursion : landing without clearance incursion : runway non adherence : company policies non adherence : published procedure non adherence : far other anomaly other anomaly other
Independent Detector	other controllera other controllerb
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

We had been cleared for a visual approach to runway 34L at seatac. Approach kept us high (6000 ft, 10 mi out) for traffic that we were to follow. We did not receive or acknowledge a handoff to tower. After an uneventful landing on runway 34L, approach control told us to contact tower. Tower cleared us to cross runway 34R and asked where we had been. Basically, we landed without clearance. I believe that being held up high and close-in kept us busy getting the jet down while looking for traffic. Both of us were shocked when we discovered approach control still in the #1 VHF after landing. Bottom line: even when it's cavu, when you're busy, you can't let your guard down. Simple reminders like turning on the outboard landing lights after receiving landing clearance, are good reminders. Perhaps adding 'landing clearance' as a final item to the landing checklist would help.

Original NASA ASRS Text

Title: RWY INCURSION WHEN THE FLC OF A B737-400 LWOC, OFF FREQ FROM THE TWR AT SEA, WA.

Narrative: WE HAD BEEN CLRED FOR A VISUAL APCH TO RWY 34L AT SEATAC. APCH KEPT US HIGH (6000 FT, 10 MI OUT) FOR TFC THAT WE WERE TO FOLLOW. WE DID NOT RECEIVE OR ACKNOWLEDGE A HDOF TO TWR. AFTER AN UNEVENTFUL LNDG ON RWY 34L, APCH CTL TOLD US TO CONTACT TWR. TWR CLRED US TO CROSS RWY 34R AND ASKED WHERE WE HAD BEEN. BASICALLY, WE LANDED WITHOUT CLRNC. I BELIEVE THAT BEING HELD UP HIGH AND CLOSE-IN KEPT US BUSY GETTING THE JET DOWN WHILE LOOKING FOR TFC. BOTH OF US WERE SHOCKED WHEN WE DISCOVERED APCH CTL STILL IN THE #1 VHF AFTER LNDG. BOTTOM LINE: EVEN WHEN IT'S CAVU, WHEN YOU'RE BUSY, YOU CAN'T LET YOUR GUARD DOWN. SIMPLE REMINDERS LIKE TURNING ON THE OUTBOARD LNDG LIGHTS AFTER RECEIVING LNDG CLRNC, ARE GOOD REMINDERS. PERHAPS ADDING 'LNDG CLRNC' AS A FINAL ITEM TO THE LNDG CHKLIST WOULD HELP.

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.

Runway incursion when the flight crew of a B737-400 landing without clearance, off frequency from the tower at sea, wa.