Narrative:

Scheduled flight from efd to iah. Multiple frequency changes and company calls required for a very short flight. I was new to iah area and did not know all of the approach frequencys. Read back XA25 for approach frequency, and was supposed to switch to AB05. Tried multiple contacts and then switched to previous frequency and then again read back XA25. Again no contact. So once again switched back to previous controller. This time was corrected on frequency change. By the time we re-established communication we were through runway 27 final and used TCASII and visual maneuvering to stay clear of traffic while reestablishing communication. Once establishing radio contact we were vectored back to ILS course. No known traffic conflicts occurred.

Google
 

Original NASA ASRS Text

Title: LESS EXPERIENCED FO HAS DIFFICULTY KEEPING TRACK OF ASSIGNED FREQS ON APCH CTL, RESULTING IN TRACK DEV.

Narrative: SCHEDULED FLT FROM EFD TO IAH. MULTIPLE FREQ CHANGES AND COMPANY CALLS REQUIRED FOR A VERY SHORT FLT. I WAS NEW TO IAH AREA AND DID NOT KNOW ALL OF THE APCH FREQS. READ BACK XA25 FOR APCH FREQ, AND WAS SUPPOSED TO SWITCH TO AB05. TRIED MULTIPLE CONTACTS AND THEN SWITCHED TO PREVIOUS FREQ AND THEN AGAIN READ BACK XA25. AGAIN NO CONTACT. SO ONCE AGAIN SWITCHED BACK TO PREVIOUS CTLR. THIS TIME WAS CORRECTED ON FREQ CHANGE. BY THE TIME WE RE-ESTABLISHED COM WE WERE THROUGH RWY 27 FINAL AND USED TCASII AND VISUAL MANEUVERING TO STAY CLR OF TFC WHILE REESTABLISHING COM. ONCE ESTABLISHING RADIO CONTACT WE WERE VECTORED BACK TO ILS COURSE. NO KNOWN TFC CONFLICTS OCCURRED.

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.