Air carrier lands without contacting tower at mslp, first officer.

Attributes
ACN	466570
Time
Date	200003
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mslp.airport
State Reference	FO
Altitude	agl single value : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mslp.tower
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach landing : roll
Route In Use	arrival star : lapaz.2
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : private pilot : instrument pilot : flight engineer pilot : commercial pilot : atp pilot : multi engine
Experience	flight time last 90 days : 180 flight time total : 7000 flight time type : 450
ASRS Report	466570
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 150 flight time total : 7000 flight time type : 3000
ASRS Report	466281
Events
Anomaly	incursion : landing without clearance non adherence : published procedure non adherence : company policies
Independent Detector	other flight crewa other flight crewb
Resolutory Action	none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

We were flying atl to sal (mslp) san salvador, el salvador. ATIS told us to expect lapaz 2 STAR to localizer runway 7 circle runway 25. While descending over high terrain north of the field, approach gave us a vector after vsy VOR direct to the field for a left downwind for runway 25. Due to the shorter route we had to hurry down. We spotted the field and were cleared a visual runway 25. Approach told us to contact tower in a heavy hispanic accent. In my haste to change the FMS/map over to runway 25 from the STAR, run the checklist and contact tower, I set the radio to tower frequency and became distraction before checking in. I was also concerned about high terrain to the east that was not visible due to haze. During landing roll, I realized our problem, switched to tower frequency and talked to tower. There were no traffic conflicts. I will never again allow myself to become so distraction, especially by the FMS, during a compressed arrival. I now use a dedicated 'cleared to land' switch technique to ensure this does not happen again.

Original NASA ASRS Text

Title: ACR LANDS WITHOUT CONTACTING TWR AT MSLP, FO.

Narrative: WE WERE FLYING ATL TO SAL (MSLP) SAN SALVADOR, EL SALVADOR. ATIS TOLD US TO EXPECT LAPAZ 2 STAR TO LOC RWY 7 CIRCLE RWY 25. WHILE DSNDING OVER HIGH TERRAIN N OF THE FIELD, APCH GAVE US A VECTOR AFTER VSY VOR DIRECT TO THE FIELD FOR A L DOWNWIND FOR RWY 25. DUE TO THE SHORTER RTE WE HAD TO HURRY DOWN. WE SPOTTED THE FIELD AND WERE CLRED A VISUAL RWY 25. APCH TOLD US TO CONTACT TWR IN A HVY HISPANIC ACCENT. IN MY HASTE TO CHANGE THE FMS/MAP OVER TO RWY 25 FROM THE STAR, RUN THE CHKLIST AND CONTACT TWR, I SET THE RADIO TO TWR FREQ AND BECAME DISTR BEFORE CHKING IN. I WAS ALSO CONCERNED ABOUT HIGH TERRAIN TO THE E THAT WAS NOT VISIBLE DUE TO HAZE. DURING LNDG ROLL, I REALIZED OUR PROB, SWITCHED TO TWR FREQ AND TALKED TO TWR. THERE WERE NO TFC CONFLICTS. I WILL NEVER AGAIN ALLOW MYSELF TO BECOME SO DISTR, ESPECIALLY BY THE FMS, DURING A COMPRESSED ARR. I NOW USE A DEDICATED 'CLRED TO LAND' SWITCH TECHNIQUE TO ENSURE THIS DOES NOT HAPPEN AGAIN.

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.