37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 362370 |
Time | |
Date | 199702 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : wal airport : man |
State Reference | FO |
Altitude | msl bound lower : 6000 msl bound upper : 6000 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : man |
Operator | common carrier : air carrier |
Make Model Name | L-1011-500 Series |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other descent : approach |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : flight engineer pilot : instrument pilot : atp pilot : commercial |
Experience | flight time last 90 days : 180 flight time total : 6500 flight time type : 1300 |
ASRS Report | 362370 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : second officer |
Qualification | pilot : instrument pilot : flight engineer pilot : commercial |
Experience | flight time last 90 days : 180 flight time total : 5500 flight time type : 300 |
ASRS Report | 362501 |
Events | |
Anomaly | non adherence : clearance non adherence : far other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | flight crew : became reoriented other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation other |
Narrative:
On switching to london control, we were told to expect wal, mirsi for arrival into manchester, united kingdom, and given vectors at about liffy that took us north of the mirib STAR (which we had not been cleared for). Manchester approach control continued giving us vectors which took us nne of wal. At this point we thought we were being vectored to the airport for landing. A few mi prior to reaching mirsi, still on vectors (we had not been told the vectors we were being given were for mirsi) we were told to expect to hold at mirsi for about 1 turn. Very shortly thereafter we were told to track 100 degrees to mirsi for the hold. We started the turn toward 100 degrees and could see that that heading actually appeared to take us away to the east from mirsi, so we turned back to the northeast to reacquire the wal 065 degree radial. We could not RNAV to mirsi as the INS platforms had drifted approximately 2 mi in the 6.5 hour flight. The initial call to 'track 100 degrees to mirsi' therefore caused a moment of confusion in the cockpit as to our exact position. When we decided that we knew where we were and that track 100 degrees wasn't going to work, we were 2 mi past mirsi and were called by approach telling us that. The flight was met by an ATC staff member who told us that no conflict was created and he wanted to know what had happened. Supplemental information from acn 362501: after our 7.5 hour flight, thus far the INS had drifted about 1-2 NM when we checked it as we overflew dublin VOR. Therefore, when xchking the INS to the west/P mirsi it appeared to be slightly off. The captain selected radio navigation instead as he was passing through the 65 degree outbound radial for wal VOR. He then selected heading and turned to intercept the holding radial (65 degrees off of wal).
Original NASA ASRS Text
Title: AN ACR L1011 FLC GETS OFF COURSE AND OVERSHOOTS THEIR HOLDING FIX WHILE ENTERING A HOLDING PATTERN NEAR MANCHESTER, UNITED KINGDOM. THE FLC WAS USING THEIR INS TO NAV WHEN IT HAD A KNOWN ERROR AND VOR WAS AVAILABLE.
Narrative: ON SWITCHING TO LONDON CTL, WE WERE TOLD TO EXPECT WAL, MIRSI FOR ARR INTO MANCHESTER, UNITED KINGDOM, AND GIVEN VECTORS AT ABOUT LIFFY THAT TOOK US N OF THE MIRIB STAR (WHICH WE HAD NOT BEEN CLRED FOR). MANCHESTER APCH CTL CONTINUED GIVING US VECTORS WHICH TOOK US NNE OF WAL. AT THIS POINT WE THOUGHT WE WERE BEING VECTORED TO THE ARPT FOR LNDG. A FEW MI PRIOR TO REACHING MIRSI, STILL ON VECTORS (WE HAD NOT BEEN TOLD THE VECTORS WE WERE BEING GIVEN WERE FOR MIRSI) WE WERE TOLD TO EXPECT TO HOLD AT MIRSI FOR ABOUT 1 TURN. VERY SHORTLY THEREAFTER WE WERE TOLD TO TRACK 100 DEGS TO MIRSI FOR THE HOLD. WE STARTED THE TURN TOWARD 100 DEGS AND COULD SEE THAT THAT HDG ACTUALLY APPEARED TO TAKE US AWAY TO THE E FROM MIRSI, SO WE TURNED BACK TO THE NE TO REACQUIRE THE WAL 065 DEG RADIAL. WE COULD NOT RNAV TO MIRSI AS THE INS PLATFORMS HAD DRIFTED APPROX 2 MI IN THE 6.5 HR FLT. THE INITIAL CALL TO 'TRACK 100 DEGS TO MIRSI' THEREFORE CAUSED A MOMENT OF CONFUSION IN THE COCKPIT AS TO OUR EXACT POS. WHEN WE DECIDED THAT WE KNEW WHERE WE WERE AND THAT TRACK 100 DEGS WASN'T GOING TO WORK, WE WERE 2 MI PAST MIRSI AND WERE CALLED BY APCH TELLING US THAT. THE FLT WAS MET BY AN ATC STAFF MEMBER WHO TOLD US THAT NO CONFLICT WAS CREATED AND HE WANTED TO KNOW WHAT HAD HAPPENED. SUPPLEMENTAL INFO FROM ACN 362501: AFTER OUR 7.5 HR FLT, THUS FAR THE INS HAD DRIFTED ABOUT 1-2 NM WHEN WE CHKED IT AS WE OVERFLEW DUBLIN VOR. THEREFORE, WHEN XCHKING THE INS TO THE W/P MIRSI IT APPEARED TO BE SLIGHTLY OFF. THE CAPT SELECTED RADIO NAV INSTEAD AS HE WAS PASSING THROUGH THE 65 DEG OUTBOUND RADIAL FOR WAL VOR. HE THEN SELECTED HDG AND TURNED TO INTERCEPT THE HOLDING RADIAL (65 DEGS OFF OF WAL).
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.