B757 advised approach control had runway 12 in sight. Cleared for visual approach, contact tower. Changed to tower but failed to contact account high on approach and had a strong crosswind. On rollout made contact with tower and advised no conflict.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	354183
Time
Date	199611
Day	Fri
Local Time Of Day	0001 To 0600
Place
Locale Reference	atc facility : iad
State Reference	VA
Altitude	msl bound lower : 3000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : dca tower : iad
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Route In Use	approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	354183
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	incursion : landing without clearance non adherence : clearance non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

At 3000 ft and approximately 8 mi from the airport, we told iad approach we had runway 12 in sight. Approach cleared us for a visual approach to runway 12 and to contact iad tower on frequency 120.1. At this point we were a little high and had a 25 KT tailwind. As I changed to tower frequency we were discussing the tailwind and extending flaps and gear. At 1000 ft the tailwind had swung mostly to crosswind and we were just getting into the slot. As we were touching down on runway 12, I realized I had not checked in with the tower. On rollout, we asked tower if we had caused a problem and the controller said no, and that we were the only aircraft being worked by approach and tower. This occurred at XA00 local time at the end of a long 3-LEG duty day. There were never any other xmissions on tower frequency nor did the tower query us as to whether we were on the frequency. I allowed myself to become distraction by our situation at a point where I should have been checking in with tower.

Original NASA ASRS Text

Title: B757 ADVISED APCH CTL HAD RWY 12 IN SIGHT. CLRED FOR VISUAL APCH, CONTACT TWR. CHANGED TO TWR BUT FAILED TO CONTACT ACCOUNT HIGH ON APCH AND HAD A STRONG XWIND. ON ROLLOUT MADE CONTACT WITH TWR AND ADVISED NO CONFLICT.

Narrative: AT 3000 FT AND APPROX 8 MI FROM THE ARPT, WE TOLD IAD APCH WE HAD RWY 12 IN SIGHT. APCH CLRED US FOR A VISUAL APCH TO RWY 12 AND TO CONTACT IAD TWR ON FREQ 120.1. AT THIS POINT WE WERE A LITTLE HIGH AND HAD A 25 KT TAILWIND. AS I CHANGED TO TWR FREQ WE WERE DISCUSSING THE TAILWIND AND EXTENDING FLAPS AND GEAR. AT 1000 FT THE TAILWIND HAD SWUNG MOSTLY TO XWIND AND WE WERE JUST GETTING INTO THE SLOT. AS WE WERE TOUCHING DOWN ON RWY 12, I REALIZED I HAD NOT CHKED IN WITH THE TWR. ON ROLLOUT, WE ASKED TWR IF WE HAD CAUSED A PROB AND THE CTLR SAID NO, AND THAT WE WERE THE ONLY ACFT BEING WORKED BY APCH AND TWR. THIS OCCURRED AT XA00 LCL TIME AT THE END OF A LONG 3-LEG DUTY DAY. THERE WERE NEVER ANY OTHER XMISSIONS ON TWR FREQ NOR DID THE TWR QUERY US AS TO WHETHER WE WERE ON THE FREQ. I ALLOWED MYSELF TO BECOME DISTR BY OUR SIT AT A POINT WHERE I SHOULD HAVE BEEN CHKING IN WITH TWR.

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.