37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 294044 |
Time | |
Date | 199501 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : sea |
State Reference | WA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : sea tower : sea |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach landing other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
ASRS Report | 294044 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : clearance other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Air carrier X given multiple instructions by approach control to intercept ILS runway 16R at seattle. Included was heading, altitude, cleared to intercept and to speed instructions 210 KTS from mgnum to anvil and 170 KTS from anvil to parkk. This required multiple xmissions to confirm. I don't recall being given the instruction to switch to tower. After parkk we slowed, configured for landing, completed checklist and landed. After rollout and clearing the runway 16R and holding short of runway 16L we realized we had not switched to tower and had landed without clearance. Tower controller gave us clearance though we did not respond and kept us safe. Suggest clear procedures for switching to tower on approach. As every airport is different, perhaps a standardized procedure could be established. Also, frequently, approach control will issue as many as 5 specific commands in 1 transmission while we pilots are trying to turn, level, slow and set our instruments (ie, high workload times). This entire process could be simplified and standardized.
Original NASA ASRS Text
Title: ACR X FAILED TO CHANGE FREQ TO OM AND LANDED WITHOUT CLRNC. PLTDEV.
Narrative: ACR X GIVEN MULTIPLE INSTRUCTIONS BY APCH CTL TO INTERCEPT ILS RWY 16R AT SEATTLE. INCLUDED WAS HDG, ALT, CLRED TO INTERCEPT AND TO SPD INSTRUCTIONS 210 KTS FROM MGNUM TO ANVIL AND 170 KTS FROM ANVIL TO PARKK. THIS REQUIRED MULTIPLE XMISSIONS TO CONFIRM. I DON'T RECALL BEING GIVEN THE INSTRUCTION TO SWITCH TO TWR. AFTER PARKK WE SLOWED, CONFIGURED FOR LNDG, COMPLETED CHKLIST AND LANDED. AFTER ROLLOUT AND CLRING THE RWY 16R AND HOLDING SHORT OF RWY 16L WE REALIZED WE HAD NOT SWITCHED TO TWR AND HAD LANDED WITHOUT CLRNC. TWR CTLR GAVE US CLRNC THOUGH WE DID NOT RESPOND AND KEPT US SAFE. SUGGEST CLR PROCS FOR SWITCHING TO TWR ON APCH. AS EVERY ARPT IS DIFFERENT, PERHAPS A STANDARDIZED PROC COULD BE ESTABLISHED. ALSO, FREQUENTLY, APCH CTL WILL ISSUE AS MANY AS 5 SPECIFIC COMMANDS IN 1 XMISSION WHILE WE PLTS ARE TRYING TO TURN, LEVEL, SLOW AND SET OUR INSTS (IE, HIGH WORKLOAD TIMES). THIS ENTIRE PROCESS COULD BE SIMPLIFIED AND STANDARDIZED.
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.