AN NMAC OCCURS OFF THE '34 SET' OF RWYS AT SEA; WA.

1999-03 · NASA ASRS report 435690

Date: 1999-03 · Aircraft: Commercial Fixed Wing

Anomalies: conflict-nmac|deviation-discrepancy-procedural-clearance|other-unauth-tkoff

Synopsis

AN NMAC OCCURS OFF THE '34 SET' OF RWYS AT SEA; WA.

Narrative

CAPT'S CDU MEL'ED INOP; ALL DATA INSERTED AND READ ON FO'S CDU. ACFT AHEAD CLRED TO CROSS RWY 34R; POS AND HOLD RWY 34L. OUR FLT CLRED POS AND HOLD RWY 34R AT INTXN Q SHORTLY THEREAFTER. FMC TKOF DATA BASED ON RWY 34L; SO CAPT ASKED THAT RWY 34R BE INSERTED ON TKOF PAGE. THIS CAUSES 3 THINGS TO OCCUR: 1) REDUCED PWR SETTING REVERTS TO MAX. 2) TKOF SPDS DELETED. 3) INITIAL LNAV LEG LOST LEAVING A LEG DISCONTINUITY. AS WE TOOK THE ACTIVE RWY AT INTXN Q; AND AS I BEGAN LOADING NEW NUMBERS; TWR CLRED US FOR TKOF AS FOLLOWS: 'CLRED FOR IMMEDIATE TKOF TFC ON A 2 1/2 MI FINAL' WHICH I ACKNOWLEDGED; 'CLRED FOR TKOF RWY 34R.' NOW; RATHER THAN LEISURELY TYPING NUMBERS ON A POS AND HOLD CLRNC; WE HAD LIMITED TIME TO LEAVE THE RWY. I CONTINUED TO TYPE DURING THE INITIAL TKOF ROLL AND HAD THE FMC PROGRAMMED BY 1000 FT TKOF ROLL (ESTIMATED). IMMEDIATELY AFTER LIFTOFF; WE GOT AN RA 'MONITOR VERT SPD' AND A STEEP CLB TCASII COMMAND. TFC RESOLUTION INDICATED PRESENT POS 300 FT BELOW US (AT MAX PITCH). AFTER RA WAS RESOLVED; I INFORMED TWR OF THE SIT. THEY INFORMED ME THAT 'ROGER; THAT WAS TFC OFF THE L RWY.' THE CAPT AND I LOOKED AT EACH OTHER SOMEWHAT PERPLEXED; BECAUSE AT NO TIME DID WE EVER HEAR TKOF CLRNC GIVEN TO ACFT AND HAD NO IDEA THERE WAS A POTENTIAL CONFLICT OFF THAT RWY. TWR NEVER INFORMED US OF PRECEDING TFC. OUR CONCERN WAS THAT DUE TO THE FMC CONFUSION; MAYBE WE ASSUMED CLRNC WAS GIVEN TO US WHEN IT WAS ACTUALLY GIVEN TO THE OTHER FLT AND TWR FAILED TO NOTICE THE SIMULTANEOUS TKOF. TO THIS DAY; I HAVE NO IDEA WHAT ACFT CAUSED THE RA BECAUSE WE NEVER WERE ABLE TO VISUALLY ACQUIRE THE TARGET. IT'S VERY PUZZLING BECAUSE THE ONLY TKOF POS TFC CONFLICT I SAW PRIOR TO TKOF WAS SHORT FINAL TO THE L RWY. I NEVER SAW TFC APCHING THE R AND THUS IT APPEARS THE 'CLRED FOR IMMEDIATE TKOF' CLRNC WAS EITHER INTENDED FOR OR ACTUALLY GIVEN TO THE OTHER FLT. FOR ALL I KNOW; HOWEVER; THE OTHER FLT REMAINED ON THE RWY BECAUSE WE NEVER SAW HIM. I READ BACK 'CLRED FOR TKOF;' THE CAPT VERBALLY REPEATED IT; AND WE NEVER HEARD THE OTHER FLT ON THE RADIO. THE MORAL OF THE STORY FOR ME IS TO BE SPRING-LOADED TO STOPPING ALL COMPUTER PROGRAMMING AS THE SIT DEMANDS. SOMETIMES THE SIT CHANGES RAPIDLY AND FLEXIBILITY DEMANDS THE ABILITY TO ADAPT AS REQUIRED. AUTOMATION DEMANDS IMPACTED OUR SITUATIONAL AWARENESS DUE TO THE RAPIDLY CHANGING NATURE OF THE TKOF SCENARIO. WHETHER WE WERE IN ERROR OR NOT; WE DID LOSE TRACK OF THE OTHER ACFT AND THAT IS INEXCUSABLE.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.