37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 412180 |
Time | |
Date | 199808 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | atc facility : lrp |
State Reference | PA |
Altitude | msl bound lower : 20000 msl bound upper : 22000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny tower : msp |
Operator | common carrier : air taxi |
Make Model Name | Challenger Jet Undifferentiated or Other Model |
Operating Under FAR Part | Part 135 |
Navigation In Use | Other Other |
Flight Phase | cruise other descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 110 flight time total : 11000 flight time type : 50 |
ASRS Report | 412180 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | altitude deviation : crossing restriction not met altitude deviation : undershoot non adherence : clearance other anomaly other |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : unable |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Having been newly typed in the regional jet I am still coming up to speed with the steep profiles the company urges us to fly in dscnts to save fuel and the operation of the FMS. In programming these profiles, I was given a restr to cross a point northeast of lrp at FL200. I programmed the FMS descent and it was verified by the first officer. Unfortunately, the crossing point was dropped into the route between the wrong fixes. I did not catch the error and set myself up to blow the restr. I was so annoyed at myself for doing this and trying to figure out what went wrong, that I missed the next speed/altitude crossing at robert intersection. There are several xchks to these profiles, but they must be used to be effective (first officer xchking, visual confirmation on the mfd and legs segments, and most of all, the of 'banana' to show projected altitude along the route). I will rededicate myself to use them all!
Original NASA ASRS Text
Title: CAPT FLYING CL65 WITH ONLY 50 HRS IN TYPE WAS NOT COMPLETELY FAMILIAR IN PROGRAMMING FMS. XING POINT FOR DSCNT WAS PROGRAMMED INCORRECTLY AND MISSED. BECAME ANNOYED AND DISTR AND MISSED A SECOND SPD ALT XING.
Narrative: HAVING BEEN NEWLY TYPED IN THE REGIONAL JET I AM STILL COMING UP TO SPD WITH THE STEEP PROFILES THE COMPANY URGES US TO FLY IN DSCNTS TO SAVE FUEL AND THE OP OF THE FMS. IN PROGRAMMING THESE PROFILES, I WAS GIVEN A RESTR TO CROSS A POINT NE OF LRP AT FL200. I PROGRAMMED THE FMS DSCNT AND IT WAS VERIFIED BY THE FO. UNFORTUNATELY, THE XING POINT WAS DROPPED INTO THE RTE BTWN THE WRONG FIXES. I DID NOT CATCH THE ERROR AND SET MYSELF UP TO BLOW THE RESTR. I WAS SO ANNOYED AT MYSELF FOR DOING THIS AND TRYING TO FIGURE OUT WHAT WENT WRONG, THAT I MISSED THE NEXT SPD/ALT XING AT ROBERT INTXN. THERE ARE SEVERAL XCHKS TO THESE PROFILES, BUT THEY MUST BE USED TO BE EFFECTIVE (FO XCHKING, VISUAL CONFIRMATION ON THE MFD AND LEGS SEGMENTS, AND MOST OF ALL, THE OF 'BANANA' TO SHOW PROJECTED ALT ALONG THE RTE). I WILL REDEDICATE MYSELF TO USE THEM ALL!
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.