A commuter flight crew landed, and detected after the fact, that they did not receive a clearance to land. The captain reports fatigue, poor CRM, and that he was lulled into the use of one frequency after having that same experience with the 2 previous airports.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	339020
Time
Date	199606
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : cvg
State Reference	OH
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Navigation In Use	Other Other
Flight Phase	landing other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : atp
Experience	flight time last 90 days : 150 flight time total : 21000 flight time type : 4000
ASRS Report	339020
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	incursion : landing without clearance non adherence : far non adherence : clearance
Independent Detector	other controllera 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:

Numerous small showers, one near southeast of airport and moving southeast. Nonstandard arrival vectors, altitudes, and frequencys, and then turned #1 for a high left visual. 'Cleared visual approach runway 18L, tower will be 118.97,' I do not recall receiving 'cleared to land.' after leaving the runway, the tower said, 'stay with me, taxi to spot X, contact ramp tower.' in dialing in the frequency, it appears that we were on wrong frequency at cvg. Then we found ourself momentarily back on approach control. Afterward we thought we may have landed with approach control still on because of the language. No specific 'contact tower.' we had just come out of hts where approach, tower, ground, clearance, tower and departure used only 119.75. Also, had just been to lan where tower, ground, and clearance were all 119.9. CRM seemed weak. There was no conflicting traffic, but could have been. My first officer later reported he was fatigued.

Original NASA ASRS Text

Title: A COMMUTER FLC LANDED, AND DETECTED AFTER THE FACT, THAT THEY DID NOT RECEIVE A CLRNC TO LAND. THE CAPT RPTS FATIGUE, POOR CRM, AND THAT HE WAS LULLED INTO THE USE OF ONE FREQ AFTER HAVING THAT SAME EXPERIENCE WITH THE 2 PREVIOUS ARPTS.

Narrative: NUMEROUS SMALL SHOWERS, ONE NEAR SE OF ARPT AND MOVING SE. NONSTANDARD ARR VECTORS, ALTS, AND FREQS, AND THEN TURNED #1 FOR A HIGH L VISUAL. 'CLRED VISUAL APCH RWY 18L, TWR WILL BE 118.97,' I DO NOT RECALL RECEIVING 'CLRED TO LAND.' AFTER LEAVING THE RWY, THE TWR SAID, 'STAY WITH ME, TAXI TO SPOT X, CONTACT RAMP TWR.' IN DIALING IN THE FREQ, IT APPEARS THAT WE WERE ON WRONG FREQ AT CVG. THEN WE FOUND OURSELF MOMENTARILY BACK ON APCH CTL. AFTERWARD WE THOUGHT WE MAY HAVE LANDED WITH APCH CTL STILL ON BECAUSE OF THE LANGUAGE. NO SPECIFIC 'CONTACT TWR.' WE HAD JUST COME OUT OF HTS WHERE APCH, TWR, GND, CLRNC, TWR AND DEP USED ONLY 119.75. ALSO, HAD JUST BEEN TO LAN WHERE TWR, GND, AND CLRNC WERE ALL 119.9. CRM SEEMED WEAK. THERE WAS NO CONFLICTING TFC, BUT COULD HAVE BEEN. MY FO LATER RPTED HE WAS FATIGUED.

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.