37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 307208 |
Time | |
Date | 199506 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : msp |
State Reference | MN |
Altitude | msl bound lower : 11100 msl bound upper : 11100 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : msp |
Operator | general aviation : corporate |
Make Model Name | BAe 125 Series 800 |
Operating Under FAR Part | Part 91 |
Navigation In Use | Other Other |
Flight Phase | descent other |
Route In Use | arrival other arrival star : star |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : atp |
Experience | flight time last 90 days : 50 flight time total : 5800 flight time type : 350 |
ASRS Report | 307208 |
Person 2 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | altitude deviation : undershoot altitude deviation : crossing restriction not met non adherence : clearance |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On the NICKL2 arrival, we were cleared to cross fredy intersection at 10000 ft. I descended and crossed at approximately 11100 ft MSL. Within 4-5 mi after crossing we were at 10000 ft. I believe we were within our limits to cross a fix within 5 mi of it at the altitude assigned. The chief pilot got a call from approach and said they wondered why we didn't make the crossing. I told him we did! We did not have proper DME information to backup FMS position so this may have been the problem fredy may not have been where the FMS was showing it. That's the only thing I can think of. There was no conflict that I am aware of. Callback conversation with reporter revealed the following information: the reporter truly believed (until the completion of this callback) that there was an altitude and distance tolerance for crossing a fix. He is now mostly disabused of that notion, but will look further to reinforce this position. Msp TRACON called his employer's flight department, but did not talk to him. He has heard nothing further from the FAA. He flies the hawker 800.
Original NASA ASRS Text
Title: A CPR LTT PLT HONESTLY THOUGHT THAT THERE WAS AN ALT AND DISTANCE TOLERANCE ON XING RESTS.
Narrative: ON THE NICKL2 ARR, WE WERE CLRED TO CROSS FREDY INTXN AT 10000 FT. I DSNDED AND CROSSED AT APPROX 11100 FT MSL. WITHIN 4-5 MI AFTER XING WE WERE AT 10000 FT. I BELIEVE WE WERE WITHIN OUR LIMITS TO CROSS A FIX WITHIN 5 MI OF IT AT THE ALT ASSIGNED. THE CHIEF PLT GOT A CALL FROM APCH AND SAID THEY WONDERED WHY WE DIDN'T MAKE THE XING. I TOLD HIM WE DID! WE DID NOT HAVE PROPER DME INFO TO BACKUP FMS POS SO THIS MAY HAVE BEEN THE PROB FREDY MAY NOT HAVE BEEN WHERE THE FMS WAS SHOWING IT. THAT'S THE ONLY THING I CAN THINK OF. THERE WAS NO CONFLICT THAT I AM AWARE OF. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR TRULY BELIEVED (UNTIL THE COMPLETION OF THIS CALLBACK) THAT THERE WAS AN ALT AND DISTANCE TOLERANCE FOR XING A FIX. HE IS NOW MOSTLY DISABUSED OF THAT NOTION, BUT WILL LOOK FURTHER TO REINFORCE THIS POS. MSP TRACON CALLED HIS EMPLOYER'S FLT DEPT, BUT DID NOT TALK TO HIM. HE HAS HEARD NOTHING FURTHER FROM THE FAA. HE FLIES THE HAWKER 800.
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.