37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 331753 |
Time | |
Date | 199603 |
Day | Mon |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | airport : gtf |
State Reference | MT |
Altitude | msl bound lower : 35000 msl bound upper : 35000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zlc |
Operator | common carrier : air carrier |
Make Model Name | DC-9 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : cfi pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 6500 flight time type : 150 |
ASRS Report | 331753 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 25000 flight time type : 3000 |
ASRS Report | 331337 |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : returned to intended course or assigned course |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
The event: a fly-over of gtf (great falls, mt) while en route from msp-gtf. We overflew the field by about 20-30 mi. That was our greatest distance from the field when we realized our position. How the problem arose and contributing factors: we were given radar vectors shortly after takeoff from msp direct to gtf when able. Flight was smooth at cruise. Our location along the route was verified by VOR xchks and time. I personally realized that we were close to gtf by our flight time and flight plan but there was some question with our navaids -- we were getting some conflicting indications. No identify of lewiston VOR -- also adding to confusion was DME OTS at gtf. ATC also never notified us of our position. As we realized our position with ATC we simply were given a descent to the field and landed with no problems. Contributing to this situation was the fact it was approaching XX00 am local time, we spent 3.5 hours delayed on the ground due to a snow storm in msp, we were flying early morning hours while on duty for approximately 12 hours. Other factors: unfamiliar route. The fact that we were given radar vectors, but no information from ATC as we approached gtf. No signal from lewiston and lack of DME at gtf. The confusion actually occurred before arriving at gtf, but by the time we descended we were past gtf. There was no conflicts, or any problems on the flight, it was uneventful, other than the fact we overflew gtf. Our corrective action was to descend to the field and land. Supplemental information from acn 331337: when aware that we were at let down time, we had trouble contacting center when we finally confirmed station passage and received let down clearance we had passed gtf.
Original NASA ASRS Text
Title: DC9 FLC OVERFLIES THE DEST ARPT. SOME NAVAID PROBS.
Narrative: THE EVENT: A FLY-OVER OF GTF (GREAT FALLS, MT) WHILE ENRTE FROM MSP-GTF. WE OVERFLEW THE FIELD BY ABOUT 20-30 MI. THAT WAS OUR GREATEST DISTANCE FROM THE FIELD WHEN WE REALIZED OUR POS. HOW THE PROB AROSE AND CONTRIBUTING FACTORS: WE WERE GIVEN RADAR VECTORS SHORTLY AFTER TKOF FROM MSP DIRECT TO GTF WHEN ABLE. FLT WAS SMOOTH AT CRUISE. OUR LOCATION ALONG THE RTE WAS VERIFIED BY VOR XCHKS AND TIME. I PERSONALLY REALIZED THAT WE WERE CLOSE TO GTF BY OUR FLT TIME AND FLT PLAN BUT THERE WAS SOME QUESTION WITH OUR NAVAIDS -- WE WERE GETTING SOME CONFLICTING INDICATIONS. NO IDENT OF LEWISTON VOR -- ALSO ADDING TO CONFUSION WAS DME OTS AT GTF. ATC ALSO NEVER NOTIFIED US OF OUR POS. AS WE REALIZED OUR POS WITH ATC WE SIMPLY WERE GIVEN A DSCNT TO THE FIELD AND LANDED WITH NO PROBS. CONTRIBUTING TO THIS SIT WAS THE FACT IT WAS APCHING XX00 AM LCL TIME, WE SPENT 3.5 HRS DELAYED ON THE GND DUE TO A SNOW STORM IN MSP, WE WERE FLYING EARLY MORNING HRS WHILE ON DUTY FOR APPROX 12 HRS. OTHER FACTORS: UNFAMILIAR RTE. THE FACT THAT WE WERE GIVEN RADAR VECTORS, BUT NO INFO FROM ATC AS WE APCHED GTF. NO SIGNAL FROM LEWISTON AND LACK OF DME AT GTF. THE CONFUSION ACTUALLY OCCURRED BEFORE ARRIVING AT GTF, BUT BY THE TIME WE DSNDED WE WERE PAST GTF. THERE WAS NO CONFLICTS, OR ANY PROBS ON THE FLT, IT WAS UNEVENTFUL, OTHER THAN THE FACT WE OVERFLEW GTF. OUR CORRECTIVE ACTION WAS TO DSND TO THE FIELD AND LAND. SUPPLEMENTAL INFO FROM ACN 331337: WHEN AWARE THAT WE WERE AT LET DOWN TIME, WE HAD TROUBLE CONTACTING CTR WHEN WE FINALLY CONFIRMED STATION PASSAGE AND RECEIVED LET DOWN CLRNC WE HAD PASSED GTF.
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.