37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 489574 |
Time | |
Date | 200010 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : tpa.airport |
State Reference | FL |
Altitude | msl single value : 11000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tpa.tracon |
Operator | common carrier : air carrier |
Make Model Name | Learjet 55 |
Operating Under FAR Part | Part 135 |
Navigation In Use | other |
Flight Phase | descent : intermediate altitude |
Route In Use | arrival star : bridge 5 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 120 flight time total : 2620 flight time type : 230 |
ASRS Report | 489574 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : company policies non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance controller : issued alert |
Supplementary | |
Problem Areas | Company Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
This was the third leg of a 4 leg trip, all within the state of florida. This leg was between naples, fl, and tampa, fl -- a flight of less than 30 mins. The flight crew consisted of 2 ATP and type rated pilots in the LR55. The PNF was relatively new to the LR55, but has numerous hours in a lear 36, 35 and 31. During arrival into the tpa airport on the brdge 5 arrival, the PNF programmed our FMS for the arrival. Usually I re-verify that the FMS has been programmed correctly, but today I did not. I felt that the PNF was experienced enough with the FMS to do this task correctly. Soon after beginning the arrival over brdge intersection, the aircraft made a turn which appeared to be the right direction for the arrival, but apparently it was not. A few mins later, approach came on and asked us if we were on the arrival. To which we replied 'yes.' he stated that he did not show us on the arrival and gave us a vector to 290 degrees and vectors to final and we landed without incident. This occurred because of a few main reasons: 1) overdependence on the accuracy of the FMS. 2) failure of the crew to verify that the FMS had the proper arrival and/or fixes programmed in. 3) failure of the crew to have the 'paper' commercial chart out in plain view to follow along with, thus eliminating the possibility that the FMS flies the wrong procedure. 4) failure of the crew to properly tune and follow the flight's progress by using ground based VOR navigation. In today's 'high tech' avionics world, we, as pilots, are becoming overdependent on all the gizmos and are forgetting the old art of flying. It is imperative that today's crew back up FMS information with vors and paper methods to assure that the FMS will be doing what you have programmed it to do. Note: there were no known conflicts created by this deviation from the arrival procedure.
Original NASA ASRS Text
Title: LJ55 CREW HAD TRACK DEV IN TPA CLASS E AIRSPACE.
Narrative: THIS WAS THE THIRD LEG OF A 4 LEG TRIP, ALL WITHIN THE STATE OF FLORIDA. THIS LEG WAS BTWN NAPLES, FL, AND TAMPA, FL -- A FLT OF LESS THAN 30 MINS. THE FLC CONSISTED OF 2 ATP AND TYPE RATED PLTS IN THE LR55. THE PNF WAS RELATIVELY NEW TO THE LR55, BUT HAS NUMEROUS HRS IN A LEAR 36, 35 AND 31. DURING ARR INTO THE TPA ARPT ON THE BRDGE 5 ARR, THE PNF PROGRAMMED OUR FMS FOR THE ARR. USUALLY I RE-VERIFY THAT THE FMS HAS BEEN PROGRAMMED CORRECTLY, BUT TODAY I DID NOT. I FELT THAT THE PNF WAS EXPERIENCED ENOUGH WITH THE FMS TO DO THIS TASK CORRECTLY. SOON AFTER BEGINNING THE ARR OVER BRDGE INTXN, THE ACFT MADE A TURN WHICH APPEARED TO BE THE RIGHT DIRECTION FOR THE ARR, BUT APPARENTLY IT WAS NOT. A FEW MINS LATER, APCH CAME ON AND ASKED US IF WE WERE ON THE ARR. TO WHICH WE REPLIED 'YES.' HE STATED THAT HE DID NOT SHOW US ON THE ARR AND GAVE US A VECTOR TO 290 DEGS AND VECTORS TO FINAL AND WE LANDED WITHOUT INCIDENT. THIS OCCURRED BECAUSE OF A FEW MAIN REASONS: 1) OVERDEPENDENCE ON THE ACCURACY OF THE FMS. 2) FAILURE OF THE CREW TO VERIFY THAT THE FMS HAD THE PROPER ARR AND/OR FIXES PROGRAMMED IN. 3) FAILURE OF THE CREW TO HAVE THE 'PAPER' COMMERCIAL CHART OUT IN PLAIN VIEW TO FOLLOW ALONG WITH, THUS ELIMINATING THE POSSIBILITY THAT THE FMS FLIES THE WRONG PROC. 4) FAILURE OF THE CREW TO PROPERLY TUNE AND FOLLOW THE FLT'S PROGRESS BY USING GND BASED VOR NAV. IN TODAY'S 'HIGH TECH' AVIONICS WORLD, WE, AS PLTS, ARE BECOMING OVERDEPENDENT ON ALL THE GIZMOS AND ARE FORGETTING THE OLD ART OF FLYING. IT IS IMPERATIVE THAT TODAY'S CREW BACK UP FMS INFO WITH VORS AND PAPER METHODS TO ASSURE THAT THE FMS WILL BE DOING WHAT YOU HAVE PROGRAMMED IT TO DO. NOTE: THERE WERE NO KNOWN CONFLICTS CREATED BY THIS DEV FROM THE ARR PROC.
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.