37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 321100 |
Time | |
Date | 199511 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : tul |
State Reference | OK |
Altitude | msl bound lower : 2500 msl bound upper : 2900 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tul |
Operator | general aviation : corporate |
Make Model Name | Super King Air 200/Huron |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 75 flight time total : 6000 |
ASRS Report | 321100 |
Person 2 | |
Affiliation | Other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | altitude deviation : overshoot non adherence : clearance |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | flight crew : returned to intended course or assigned course |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After a rushed departure from tulsa international our aircraft was climbing to our assigned altitude of 2500 ft. I was flying right seat and in the process of inputting waypoints on our GPS. The PF was apparently trying to switch his navigation from VOR mode to FMS mode. When our altitude alerter chimed indicating 1000 ft to leveloff, I made a call '1000 ft to go' noting our altitude, and resumed inputting data in the GPS. The PF continued climbing and when I heard the altitude alerter chime again I looked up and noticed we were at 2900 ft. The PF then began a descent to 2500 ft. I believe what caused this occurrence was poor CRM and lack of attention on the part of the PF. All our company aircraft are crewed with 2 pilots and the PNF is responsible for setting up the navs and programming GPS's. In this case I feel the PF should have asked me to set him up how he wanted, and not tried to do it himself while being responsible for flying the aircraft. Callback conversation with reporter revealed the following information: the reporter stated he was flying the BE200. The aircraft has an advanced cockpit.
Original NASA ASRS Text
Title: FLC CLBS THROUGH ASSIGNED ALT OF 2500 FT TO 2900 FT BEFORE ALT ALERTER PROMPTED CREW TO RETURN TO 2500 FT.
Narrative: AFTER A RUSHED DEP FROM TULSA INTL OUR ACFT WAS CLBING TO OUR ASSIGNED ALT OF 2500 FT. I WAS FLYING R SEAT AND IN THE PROCESS OF INPUTTING WAYPOINTS ON OUR GPS. THE PF WAS APPARENTLY TRYING TO SWITCH HIS NAV FROM VOR MODE TO FMS MODE. WHEN OUR ALT ALERTER CHIMED INDICATING 1000 FT TO LEVELOFF, I MADE A CALL '1000 FT TO GO' NOTING OUR ALT, AND RESUMED INPUTTING DATA IN THE GPS. THE PF CONTINUED CLBING AND WHEN I HEARD THE ALT ALERTER CHIME AGAIN I LOOKED UP AND NOTICED WE WERE AT 2900 FT. THE PF THEN BEGAN A DSCNT TO 2500 FT. I BELIEVE WHAT CAUSED THIS OCCURRENCE WAS POOR CRM AND LACK OF ATTN ON THE PART OF THE PF. ALL OUR COMPANY ACFT ARE CREWED WITH 2 PLTS AND THE PNF IS RESPONSIBLE FOR SETTING UP THE NAVS AND PROGRAMMING GPS'S. IN THIS CASE I FEEL THE PF SHOULD HAVE ASKED ME TO SET HIM UP HOW HE WANTED, AND NOT TRIED TO DO IT HIMSELF WHILE BEING RESPONSIBLE FOR FLYING THE ACFT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED HE WAS FLYING THE BE200. THE ACFT HAS AN ADVANCED COCKPIT.
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.