Runway incursion. Landing without clearance from tower.

Attributes
ACN	309730
Time
Date	199506
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : mdw
State Reference	IL
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : mdw
Operator	general aviation : corporate
Make Model Name	BAe 125 Series 800
Operating Under FAR Part	Part 135
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 100 flight time total : 12300 flight time type : 1500
ASRS Report	309730
Person 2
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : landing without clearance non adherence : far other anomaly other
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:

Report damaged in mail. Callback conversation with reporter revealed the following information: aircraft was cleared for visual approach to runway 31C by approach control and to contact tower at the OM. Attention was diverted by a message to contact the FBO where they would be parking. Flight crew failed to contact the tower at OM and landed without clearance and, they didn't realize it until the reporter first officer looked at the frequencys on the approach page and saw that approach was still set. After contacting ground control for taxi instructions, they didn't say anything about the landing. During a subsequent flight the reporter again almost forgot to contact tower and made a comment to the controller to that effect, to which the controller responded 'it is a common occurrence here at mdw.' reporter thinks perhaps one of the contributing causes is being cleared for a visual approach and not telling the flight crew to contact tower at that time. Instead, being instructed to contact tower at OM when on a visual approach, leads to forgetting to call. Whereas, on an IFR approach it is not likely to be missed. Another possible factor that may contribute to the problem is the similarity of frequencys of approach control and tower, approach is 118.4 and tower is 118.7.

Original NASA ASRS Text

Title: RWY INCURSION. LNDG WITHOUT CLRNC FROM TWR.

Narrative: RPT DAMAGED IN MAIL. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: ACFT WAS CLRED FOR VISUAL APCH TO RWY 31C BY APCH CTL AND TO CONTACT TWR AT THE OM. ATTN WAS DIVERTED BY A MESSAGE TO CONTACT THE FBO WHERE THEY WOULD BE PARKING. FLC FAILED TO CONTACT THE TWR AT OM AND LANDED WITHOUT CLRNC AND, THEY DIDN'T REALIZE IT UNTIL THE RPTR FO LOOKED AT THE FREQS ON THE APCH PAGE AND SAW THAT APCH WAS STILL SET. AFTER CONTACTING GND CTL FOR TAXI INSTRUCTIONS, THEY DIDN'T SAY ANYTHING ABOUT THE LNDG. DURING A SUBSEQUENT FLT THE RPTR AGAIN ALMOST FORGOT TO CONTACT TWR AND MADE A COMMENT TO THE CTLR TO THAT EFFECT, TO WHICH THE CTLR RESPONDED 'IT IS A COMMON OCCURRENCE HERE AT MDW.' RPTR THINKS PERHAPS ONE OF THE CONTRIBUTING CAUSES IS BEING CLRED FOR A VISUAL APCH AND NOT TELLING THE FLC TO CONTACT TWR AT THAT TIME. INSTEAD, BEING INSTRUCTED TO CONTACT TWR AT OM WHEN ON A VISUAL APCH, LEADS TO FORGETTING TO CALL. WHEREAS, ON AN IFR APCH IT IS NOT LIKELY TO BE MISSED. ANOTHER POSSIBLE FACTOR THAT MAY CONTRIBUTE TO THE PROB IS THE SIMILARITY OF FREQS OF APCH CTL AND TWR, APCH IS 118.4 AND TWR IS 118.7.

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.