While on approach, a ba-32 commuter flight crew attempted to contact the tower on the wrong frequenc...

Attributes
ACN	303814
Time
Date	199505
Day	Mon
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : swf
State Reference	NY
Altitude	msl bound lower : 491 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : swf tower : ord
Operator	common carrier : air carrier
Make Model Name	Jetstream 32
Operating Under FAR Part	Part 135
Flight Phase	descent : approach descent other landing other
Route In Use	approach : visual enroute : direct enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 240 flight time total : 3345 flight time type : 1925
ASRS Report	303814
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 10000 flight time type : 4000
ASRS Report	303927
Events
Anomaly	incursion : landing without clearance non adherence : clearance non adherence : far other anomaly other other anomaly other
Independent Detector	other controllera
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

Narrative:

On may/mon/95 we left hpn for a short combination flight to swf. We were on an IFR flight plan and in new york approach control's jurisdiction. We were in VMC conditions at 3000 ft cruising to swf. The flight lasted all of about 12-15 mins and we were able to pick up swf about 12 mi out. After confirming the airport with approach control, we were cleared for the visual approach to runway 9 at swf. At this time, the captain (PNF) was talking to company on the #2 radio. I (PF) was told to contact swf tower on 121.1. The captain then returned to the #1 radio and I told him we were cleared for visual to runway 9. I then told him to call the tower as I had not checked in yet. He proceeded to call 3 times with no response. At this time, we were configuring the aircraft and on base leg for the runway. The captain then assumed that the tower was cleared as it was XA40 at night and we received no response. We proceeded to make traffic calls for the field and landed uneventfully. After clearing the runway, I called new york approach back to cancel our IFR flight plan. It was at this time the controller said to contact tower again. We said it was closed and to cancel us out. However, this time we received a different tower frequency. We immediately called the tower and idented ourselves. The tower controller was very upset and asked us to call once we got inside. We explained what had happened, but controller stated it would be written up anyway. Factors: fatigue. Late at night and thought tower was closed since we left hpn and their tower was also closed. No response either. Short flight with many checklists to run, crew was separate during these phases. Busiest time of flight, configuring aircraft, talk to company/passenger, trying to raise tower with no response. Supplemental information from acn 303927: my first officer stated that he had been cleared for the visual runway 9 at newbergh and frequency changed. He stated he had the tower frequency in the radio and requested landing checklist.

Original NASA ASRS Text

Title: WHILE ON APCH, A BA-32 COMMUTER FLC ATTEMPTED TO CONTACT THE TWR ON THE WRONG FREQ. AFTER NO RESPONSE, FLC ASSUMED THAT TWR WAS CLOSED, AND CONTINUED INTO CLASS D AND LANDED WITHOUT LNDG CLRNC.

Narrative: ON MAY/MON/95 WE LEFT HPN FOR A SHORT COMBINATION FLT TO SWF. WE WERE ON AN IFR FLT PLAN AND IN NEW YORK APCH CTL'S JURISDICTION. WE WERE IN VMC CONDITIONS AT 3000 FT CRUISING TO SWF. THE FLT LASTED ALL OF ABOUT 12-15 MINS AND WE WERE ABLE TO PICK UP SWF ABOUT 12 MI OUT. AFTER CONFIRMING THE ARPT WITH APCH CTL, WE WERE CLRED FOR THE VISUAL APCH TO RWY 9 AT SWF. AT THIS TIME, THE CAPT (PNF) WAS TALKING TO COMPANY ON THE #2 RADIO. I (PF) WAS TOLD TO CONTACT SWF TWR ON 121.1. THE CAPT THEN RETURNED TO THE #1 RADIO AND I TOLD HIM WE WERE CLRED FOR VISUAL TO RWY 9. I THEN TOLD HIM TO CALL THE TWR AS I HAD NOT CHKED IN YET. HE PROCEEDED TO CALL 3 TIMES WITH NO RESPONSE. AT THIS TIME, WE WERE CONFIGURING THE ACFT AND ON BASE LEG FOR THE RWY. THE CAPT THEN ASSUMED THAT THE TWR WAS CLRED AS IT WAS XA40 AT NIGHT AND WE RECEIVED NO RESPONSE. WE PROCEEDED TO MAKE TFC CALLS FOR THE FIELD AND LANDED UNEVENTFULLY. AFTER CLRING THE RWY, I CALLED NEW YORK APCH BACK TO CANCEL OUR IFR FLT PLAN. IT WAS AT THIS TIME THE CTLR SAID TO CONTACT TWR AGAIN. WE SAID IT WAS CLOSED AND TO CANCEL US OUT. HOWEVER, THIS TIME WE RECEIVED A DIFFERENT TWR FREQ. WE IMMEDIATELY CALLED THE TWR AND IDENTED OURSELVES. THE TWR CTLR WAS VERY UPSET AND ASKED US TO CALL ONCE WE GOT INSIDE. WE EXPLAINED WHAT HAD HAPPENED, BUT CTLR STATED IT WOULD BE WRITTEN UP ANYWAY. FACTORS: FATIGUE. LATE AT NIGHT AND THOUGHT TWR WAS CLOSED SINCE WE LEFT HPN AND THEIR TWR WAS ALSO CLOSED. NO RESPONSE EITHER. SHORT FLT WITH MANY CHKLISTS TO RUN, CREW WAS SEPARATE DURING THESE PHASES. BUSIEST TIME OF FLT, CONFIGURING ACFT, TALK TO COMPANY/PAX, TRYING TO RAISE TWR WITH NO RESPONSE. SUPPLEMENTAL INFO FROM ACN 303927: MY FO STATED THAT HE HAD BEEN CLRED FOR THE VISUAL RWY 9 AT NEWBERGH AND FREQ CHANGED. HE STATED HE HAD THE TWR FREQ IN THE RADIO AND REQUESTED LNDG CHKLIST.

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.

While on approach, a ba-32 commuter flight crew attempted to contact the tower on the wrong frequency. After no response, flight crew assumed that tower was closed, and continued into class D and landed without landing clearance.