Saab 340 lands lax without clearance.

Attributes
ACN	438020
Time
Date	199905
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Weather Elements	other
Aircraft 1
Controlling Facilities	tower : lax.tower
Operator	common carrier : air carrier
Make Model Name	SF 340B
Operating Under FAR Part	Part 121
Flight Phase	descent : approach landing : roll
Route In Use	approach : traffic pattern approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier company other government : faa government other other Other
Function	controller : local instruction : instructor observation : air carrier inspector oversight : pic
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : multi engine pilot : commercial
Events
Anomaly	incursion : landing without clearance non adherence : far non adherence : clearance
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After being vectored on to final, the controller said 'our aircraft looked good with traffic to follow and to contact tower at xxxxx intersection.' I acknowledged, and I must have gotten complacent. After landing, I looked down at the radios and saw tower frequency on standby. Immediately switching frequencys, our n-number was called and we were told to cross the parallel runway and contact ground. I'm sure the tower must have tried numerous times to contact us and wondered why, if the tower received no response, why the tower wouldn't call via landline to the approach control to try us back. It was a relatively quiet time, some haze normal to los angeles. Our common practice for a landing clearance is to turn on our taxi light. When I looked for this after coming to a complete stop, the light was in the off position. That, plus the fact tower frequency was in standby, I thought 'oh no.' no aircraft were sent around or any other deviations made to anyone else, and no other runways or txwys were crossed. The first officer was pretty new also -- only a couple of months with the company.

Original NASA ASRS Text

Title: SAAB 340 LANDS LAX WITHOUT CLRNC.

Narrative: AFTER BEING VECTORED ON TO FINAL, THE CTLR SAID 'OUR ACFT LOOKED GOOD WITH TFC TO FOLLOW AND TO CONTACT TWR AT XXXXX INTXN.' I ACKNOWLEDGED, AND I MUST HAVE GOTTEN COMPLACENT. AFTER LNDG, I LOOKED DOWN AT THE RADIOS AND SAW TWR FREQ ON STANDBY. IMMEDIATELY SWITCHING FREQS, OUR N-NUMBER WAS CALLED AND WE WERE TOLD TO CROSS THE PARALLEL RWY AND CONTACT GND. I'M SURE THE TWR MUST HAVE TRIED NUMEROUS TIMES TO CONTACT US AND WONDERED WHY, IF THE TWR RECEIVED NO RESPONSE, WHY THE TWR WOULDN'T CALL VIA LANDLINE TO THE APCH CTL TO TRY US BACK. IT WAS A RELATIVELY QUIET TIME, SOME HAZE NORMAL TO LOS ANGELES. OUR COMMON PRACTICE FOR A LNDG CLRNC IS TO TURN ON OUR TAXI LIGHT. WHEN I LOOKED FOR THIS AFTER COMING TO A COMPLETE STOP, THE LIGHT WAS IN THE OFF POS. THAT, PLUS THE FACT TWR FREQ WAS IN STANDBY, I THOUGHT 'OH NO.' NO ACFT WERE SENT AROUND OR ANY OTHER DEVS MADE TO ANYONE ELSE, AND NO OTHER RWYS OR TXWYS WERE CROSSED. THE FO WAS PRETTY NEW ALSO -- ONLY A COUPLE OF MONTHS WITH THE COMPANY.

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.