Landing B737 PIC forgets to change to tower frequency while engrossed with the emergency going on with the aircraft on approach behind his aircraft. Says frequency was too busy and distraction crew. Crew called tower by phone later.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	380420
Time
Date	199709
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : bwi
State Reference	MD
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Controlling Facilities	tower : bwi
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	descent : approach
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp pilot : flight engineer
Experience	flight time last 90 days : 150 flight time total : 10500 flight time type : 7000
ASRS Report	380420
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : commercial pilot : atp
Experience	flight time last 90 days : 120 flight time total : 13000 flight time type : 6000
ASRS Report	380278
Events
Anomaly	incursion : landing without clearance non adherence : far non adherence : published procedure other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation other

Narrative:

On approach into baltimore international we had been cleared for the visual approach to runway 10. The aircraft following us had just declared an emergency and was requesting emergency vehicles. We were on short final as all this communication was going on. The controller forgot to tell us to contact tower and we missed it ourselves with all the chatter on the frequency. As we rolled out and turned off the runway, we realized that we had not received a clearance to land. In talking with the tower on the phone later, they said they were aware of our presence and that they knew we were landing. They just had their hands full rolling the emergency equipment and talking with the emergency aircraft. We still should have noticed that we were not on tower, but the frequency was very busy and we were trying not to interfere with the emergency in progress.

Original NASA ASRS Text

Title: LNDG B737 PIC FORGETS TO CHANGE TO TWR FREQ WHILE ENGROSSED WITH THE EMER GOING ON WITH THE ACFT ON APCH BEHIND HIS ACFT. SAYS FREQ WAS TOO BUSY AND DISTR CREW. CREW CALLED TWR BY PHONE LATER.

Narrative: ON APCH INTO BALTIMORE INTL WE HAD BEEN CLRED FOR THE VISUAL APCH TO RWY 10. THE ACFT FOLLOWING US HAD JUST DECLARED AN EMER AND WAS REQUESTING EMER VEHICLES. WE WERE ON SHORT FINAL AS ALL THIS COM WAS GOING ON. THE CTLR FORGOT TO TELL US TO CONTACT TWR AND WE MISSED IT OURSELVES WITH ALL THE CHATTER ON THE FREQ. AS WE ROLLED OUT AND TURNED OFF THE RWY, WE REALIZED THAT WE HAD NOT RECEIVED A CLRNC TO LAND. IN TALKING WITH THE TWR ON THE PHONE LATER, THEY SAID THEY WERE AWARE OF OUR PRESENCE AND THAT THEY KNEW WE WERE LNDG. THEY JUST HAD THEIR HANDS FULL ROLLING THE EMER EQUIP AND TALKING WITH THE EMER ACFT. WE STILL SHOULD HAVE NOTICED THAT WE WERE NOT ON TWR, BUT THE FREQ WAS VERY BUSY AND WE WERE TRYING NOT TO INTERFERE WITH THE EMER IN PROGRESS.

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.