37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 514361 |
Time | |
Date | 200106 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : bwi.airport |
State Reference | MD |
Altitude | msl bound lower : 2900 msl bound upper : 4000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : bwi.tracon artcc : zbw.artcc |
Operator | common carrier : air taxi |
Make Model Name | Jetstream 41 |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 100 flight time total : 1300 flight time type : 200 |
ASRS Report | 514361 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | altitude deviation : overshoot non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : became reoriented |
Supplementary | |
Problem Areas | Aircraft ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Approaching bwi, the captain, acting as PNF, became busy with in-range duties (getting ATIS, calling in-range, etc), leaving me to talk to approach and fly. It being a sunny summer weekend day, there was lots of VFR traffic around. I was given several vectors and altitude changes around traffic as we approached the baltimore terminal area. My workload became very high. Finally I was given a descent to 4000 ft. The autoplt was engaged, so I set in the altitude, and intended to select 'altsel' and 'IAS,' but ended up not hitting the 'altsel' button. Therefore, the autoplt went through 4000 ft and kept on descending. I finally noticed our altitude around 2900 ft. This was due to high workload caused by traffic calls and more heading assignments. I'm not sure what could have prevented this particular screw-up. Maybe some kind of guard or light that indicates when a descent is started and 'altsel' is not selected. I know this is a reasonably common occurrence on the JS41, maybe that would help.
Original NASA ASRS Text
Title: JS41 FLC OVERSHOT ALT ON VECTORS TO BWI WHEN ALTSEL INFO IS SET BUT ALTSEL NOT ACTIVATED.
Narrative: APCHING BWI, THE CAPT, ACTING AS PNF, BECAME BUSY WITH IN-RANGE DUTIES (GETTING ATIS, CALLING IN-RANGE, ETC), LEAVING ME TO TALK TO APCH AND FLY. IT BEING A SUNNY SUMMER WEEKEND DAY, THERE WAS LOTS OF VFR TFC AROUND. I WAS GIVEN SEVERAL VECTORS AND ALT CHANGES AROUND TFC AS WE APCHED THE BALTIMORE TERMINAL AREA. MY WORKLOAD BECAME VERY HIGH. FINALLY I WAS GIVEN A DSCNT TO 4000 FT. THE AUTOPLT WAS ENGAGED, SO I SET IN THE ALT, AND INTENDED TO SELECT 'ALTSEL' AND 'IAS,' BUT ENDED UP NOT HITTING THE 'ALTSEL' BUTTON. THEREFORE, THE AUTOPLT WENT THROUGH 4000 FT AND KEPT ON DSNDING. I FINALLY NOTICED OUR ALT AROUND 2900 FT. THIS WAS DUE TO HIGH WORKLOAD CAUSED BY TFC CALLS AND MORE HEADING ASSIGNMENTS. I'M NOT SURE WHAT COULD HAVE PREVENTED THIS PARTICULAR SCREW-UP. MAYBE SOME KIND OF GUARD OR LIGHT THAT INDICATES WHEN A DSCNT IS STARTED AND 'ALTSEL' IS NOT SELECTED. I KNOW THIS IS A REASONABLY COMMON OCCURRENCE ON THE JS41, MAYBE THAT WOULD HELP.
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.