37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 453250 |
Time | |
Date | 199910 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : ind.airport |
State Reference | IN |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : ind.tracon tower : ind.tower |
Operator | general aviation : corporate |
Make Model Name | Citation V |
Operating Under FAR Part | Part 91 |
Navigation In Use | ils localizer & glide slope : 23r |
Flight Phase | descent : approach landing : roll |
Route In Use | approach : instrument precision approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 13000 flight time type : 300 |
ASRS Report | 453250 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | incursion : landing without clearance non adherence : company policies non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Landed at ind runway 23R without landing clearance. We were vectored for a visual approach behind other traffic. Within 10-15 mi of the airport, while being vectored, I looked up the ind tower and ground frequencys. Being close to the airport, with TA's, checklist duties and requests by the PF (also the PIC) when approach control advised cleared for the visual approach to runway 23L, no frequency change was given, which might have cued us to switch frequencys to the tower. As it was, with the distrs, the frequencys I had looked up were never tuned in. The distrs which included airspeed, sink rate, and altitude calls on final, left no cues that the tower had not been contacted. I do not absolve myself of blame and make no excuses. The rushed situation in the terminal area, couple with the numerous distrs -- particularly in good WX -- assure mistakes over time. This is particular true after a long duty day, as this was. The day began at XA30 and the incident took place 10 hours later.
Original NASA ASRS Text
Title: C560 CREW LANDED WITHOUT CLRNC AT IND.
Narrative: LANDED AT IND RWY 23R WITHOUT LNDG CLRNC. WE WERE VECTORED FOR A VISUAL APCH BEHIND OTHER TFC. WITHIN 10-15 MI OF THE ARPT, WHILE BEING VECTORED, I LOOKED UP THE IND TWR AND GND FREQS. BEING CLOSE TO THE ARPT, WITH TA'S, CHKLIST DUTIES AND REQUESTS BY THE PF (ALSO THE PIC) WHEN APCH CTL ADVISED CLRED FOR THE VISUAL APCH TO RWY 23L, NO FREQ CHANGE WAS GIVEN, WHICH MIGHT HAVE CUED US TO SWITCH FREQS TO THE TWR. AS IT WAS, WITH THE DISTRS, THE FREQS I HAD LOOKED UP WERE NEVER TUNED IN. THE DISTRS WHICH INCLUDED AIRSPD, SINK RATE, AND ALT CALLS ON FINAL, LEFT NO CUES THAT THE TWR HAD NOT BEEN CONTACTED. I DO NOT ABSOLVE MYSELF OF BLAME AND MAKE NO EXCUSES. THE RUSHED SIT IN THE TERMINAL AREA, COUPLE WITH THE NUMEROUS DISTRS -- PARTICULARLY IN GOOD WX -- ASSURE MISTAKES OVER TIME. THIS IS PARTICULAR TRUE AFTER A LONG DUTY DAY, AS THIS WAS. THE DAY BEGAN AT XA30 AND THE INCIDENT TOOK PLACE 10 HRS LATER.
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.