An MU2 pilot forgot his assigned frequency and contacted bfi tower to reestablish communication in S...

Attributes
ACN	597628
Time
Date	200310
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : bfi.airport
State Reference	WA
Altitude	msl single value : 5000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : s46.tracon tower : bfi.tower
Operator	common carrier : air taxi
Make Model Name	MU-2 Undifferentiated or Other Model
Operating Under FAR Part	Part 135
Flight Phase	descent : intermediate altitude descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : single pilot
Qualification	pilot : multi engine pilot : atp
Experience	flight time last 90 days : 120 flight time total : 7300 flight time type : 720
ASRS Report	597628
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	non adherence : clearance non adherence : far non adherence : published procedure
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

Was being handled by seattle approach on vectors for a visual approach to runway 31L at bfi. Assigned 5000 ft MSL, on an easterly heading (left base for runway 31L). Given frequency change to another approach controller and told to expect lower altitude from them. While turning the radios, inadvertently changed frequencys to bfi tower and ground control (trying to plan ahead for the final) and did not remember the approach control frequency. I realized immediately I was out of communication with approach and called tower for some help. I did not change heading or altitude until tower cleared me for landing on runway 31L (I had reported runway in sight). I was very concerned by the foul up on my part, but concentrated on the final approach and landing. While taxiing to parking, was asked by ground to call seattle approach supervisor after shut down. I complied. In retrospect, I realized I was thinking too far ahead and set myself up for the mistake by not going step by step. I believe that contacting tower was the fastest way to get back in the system, and I was VMC at the time, but it was scary to think what would have been the case in IMC. I will slow down in the future.

Original NASA ASRS Text

Title: AN MU2 PLT FORGOT HIS ASSIGNED FREQ AND CONTACTED BFI TWR TO REESTABLISH COM IN S46 AIRSPACE.

Narrative: WAS BEING HANDLED BY SEATTLE APCH ON VECTORS FOR A VISUAL APCH TO RWY 31L AT BFI. ASSIGNED 5000 FT MSL, ON AN EASTERLY HEADING (L BASE FOR RWY 31L). GIVEN FREQ CHANGE TO ANOTHER APCH CTLR AND TOLD TO EXPECT LOWER ALT FROM THEM. WHILE TURNING THE RADIOS, INADVERTENTLY CHANGED FREQS TO BFI TWR AND GND CTL (TRYING TO PLAN AHEAD FOR THE FINAL) AND DID NOT REMEMBER THE APCH CTL FREQ. I REALIZED IMMEDIATELY I WAS OUT OF COM WITH APCH AND CALLED TWR FOR SOME HELP. I DID NOT CHANGE HEADING OR ALT UNTIL TWR CLRED ME FOR LNDG ON RWY 31L (I HAD RPTED RWY IN SIGHT). I WAS VERY CONCERNED BY THE FOUL UP ON MY PART, BUT CONCENTRATED ON THE FINAL APCH AND LNDG. WHILE TAXIING TO PARKING, WAS ASKED BY GND TO CALL SEATTLE APCH SUPVR AFTER SHUT DOWN. I COMPLIED. IN RETROSPECT, I REALIZED I WAS THINKING TOO FAR AHEAD AND SET MYSELF UP FOR THE MISTAKE BY NOT GOING STEP BY STEP. I BELIEVE THAT CONTACTING TWR WAS THE FASTEST WAY TO GET BACK IN THE SYS, AND I WAS VMC AT THE TIME, BUT IT WAS SCARY TO THINK WHAT WOULD HAVE BEEN THE CASE IN IMC. I WILL SLOW DOWN IN THE FUTURE.

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.

An MU2 pilot forgot his assigned frequency and contacted bfi tower to reestablish communication in S46 airspace.