37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 540438 |
Time | |
Date | 200203 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : srq.airport |
State Reference | FL |
Altitude | msl bound lower : 0 msl bound upper : 4500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tpa.tracon tower : srq.tower tower : psp.tower |
Operator | general aviation : corporate |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Navigation In Use | other |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure sid : scrasota 1 |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : srq.tower |
Operator | Other |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | other : ns |
Flight Phase | descent : approach |
Route In Use | approach : instrument precision |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 110 flight time total : 6568 flight time type : 1535 |
ASRS Report | 540438 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | non adherence : published procedure non adherence : far non adherence : company policies non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance controller : issued alert none taken : detected after the fact |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Company FAA Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After a refueling delay, we hurried to take off. During the delay, a wind shift resulted in a 180 degree change of runway use. As PNF began to brief the departure on runway 14, PF corrected him, saying 'no, we're on runway 32.' PNF hesitated, then began the brief, again using runway 14. PF again stopped him, saying 'no, they changed runways -- we're on runway 32.' PNF put aside the corrected SID plate (away from PF) and called ground for taxi. As we taxied, ground told us to hurry through an intersection with a runway for landing traffic on 1 mi final, which after evaluating our spacing, we did. As we completed our taxi checks, we stopped behind a commercial carrier, #2 in sequence, expecting to brief the departure. Tower advised us to continue taxi past the airliner who was awaiting WX delay clearance, and cleared us for takeoff. As PF lined up, he asked if PNF was ready. PNF remarked 'noise abatement procedures, 15000 ft and then flaps up?' somewhat surprised at this first mention of noise abatement, PF replied 'uh, yeah.' takeoff was in accordance with recommended practice for noise abatement, straight ahead. After 1500 ft AGL and flaps were retracted, PF asked about what ground track was supposed to be. PNF then pulled out the SID and began reading. PF called departure and told them he was 'runway heading passing 2000 ft' (or what altitude it actually was). Departure responded we were not given runway heading, we were supposed to fly the SID with a turn at 0.9 DME to follow a radial about 30 degrees off heading, but told us to fly present heading and climb to ....' PF failed to review SID prior to taxi, expecting PNF to brief it. PNF was miffed when PF corrected his brief twice in a row, and delayed brief to verify the runway in use. Taxi checklist activity and other traffic (expedited runway crossing) and airliner at runway end resulted in our being cleared for takeoff before we expected. PF's 'are you ready?' may have been perceived more of a personal challenge to PNF than was intended, in light of events during aborted SID brief before taxi. PNF was unwilling to say he wasn't ready, even though he felt rushed (machismo?). PF inappropriately continued the takeoff after sensing PNF may not have been ready, and wasn't ready himself, without a SID brief, must expecting runway heading and noise abatement procedures.
Original NASA ASRS Text
Title: BE40 JET CREW HAD A TRACK DEV DEPARTING SRQ.
Narrative: AFTER A REFUELING DELAY, WE HURRIED TO TAKE OFF. DURING THE DELAY, A WIND SHIFT RESULTED IN A 180 DEG CHANGE OF RWY USE. AS PNF BEGAN TO BRIEF THE DEP ON RWY 14, PF CORRECTED HIM, SAYING 'NO, WE'RE ON RWY 32.' PNF HESITATED, THEN BEGAN THE BRIEF, AGAIN USING RWY 14. PF AGAIN STOPPED HIM, SAYING 'NO, THEY CHANGED RWYS -- WE'RE ON RWY 32.' PNF PUT ASIDE THE CORRECTED SID PLATE (AWAY FROM PF) AND CALLED GND FOR TAXI. AS WE TAXIED, GND TOLD US TO HURRY THROUGH AN INTXN WITH A RWY FOR LNDG TFC ON 1 MI FINAL, WHICH AFTER EVALUATING OUR SPACING, WE DID. AS WE COMPLETED OUR TAXI CHKS, WE STOPPED BEHIND A COMMERCIAL CARRIER, #2 IN SEQUENCE, EXPECTING TO BRIEF THE DEP. TWR ADVISED US TO CONTINUE TAXI PAST THE AIRLINER WHO WAS AWAITING WX DELAY CLRNC, AND CLRED US FOR TKOF. AS PF LINED UP, HE ASKED IF PNF WAS READY. PNF REMARKED 'NOISE ABATEMENT PROCS, 15000 FT AND THEN FLAPS UP?' SOMEWHAT SURPRISED AT THIS FIRST MENTION OF NOISE ABATEMENT, PF REPLIED 'UH, YEAH.' TKOF WAS IN ACCORDANCE WITH RECOMMENDED PRACTICE FOR NOISE ABATEMENT, STRAIGHT AHEAD. AFTER 1500 FT AGL AND FLAPS WERE RETRACTED, PF ASKED ABOUT WHAT GND TRACK WAS SUPPOSED TO BE. PNF THEN PULLED OUT THE SID AND BEGAN READING. PF CALLED DEP AND TOLD THEM HE WAS 'RWY HDG PASSING 2000 FT' (OR WHAT ALT IT ACTUALLY WAS). DEP RESPONDED WE WERE NOT GIVEN RWY HDG, WE WERE SUPPOSED TO FLY THE SID WITH A TURN AT 0.9 DME TO FOLLOW A RADIAL ABOUT 30 DEGS OFF HDG, BUT TOLD US TO FLY PRESENT HDG AND CLB TO ....' PF FAILED TO REVIEW SID PRIOR TO TAXI, EXPECTING PNF TO BRIEF IT. PNF WAS MIFFED WHEN PF CORRECTED HIS BRIEF TWICE IN A ROW, AND DELAYED BRIEF TO VERIFY THE RWY IN USE. TAXI CHKLIST ACTIVITY AND OTHER TFC (EXPEDITED RWY XING) AND AIRLINER AT RWY END RESULTED IN OUR BEING CLRED FOR TKOF BEFORE WE EXPECTED. PF'S 'ARE YOU READY?' MAY HAVE BEEN PERCEIVED MORE OF A PERSONAL CHALLENGE TO PNF THAN WAS INTENDED, IN LIGHT OF EVENTS DURING ABORTED SID BRIEF BEFORE TAXI. PNF WAS UNWILLING TO SAY HE WASN'T READY, EVEN THOUGH HE FELT RUSHED (MACHISMO?). PF INAPPROPRIATELY CONTINUED THE TKOF AFTER SENSING PNF MAY NOT HAVE BEEN READY, AND WASN'T READY HIMSELF, WITHOUT A SID BRIEF, MUST EXPECTING RWY HDG AND NOISE ABATEMENT PROCS.
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.