NEAR GND COLLISION BTWN A TAXIING CRJ AND A CITATION II WHO HAD TAKEN OFF ON TXWY U AT RIC; VA.

2004-01 · NASA ASRS report 606541

Date: 2004-01 · Aircraft: Regional Jet CL65; Undifferentiated or Other Model · Phase: taxi

Anomalies: atc-issue-all-types|conflict-ground-conflict|critical|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-clearance|ground-incursion-taxiway|inflight-event-encounter-weather-turbulence|other-txwy-tkof

Synopsis

NEAR GND COLLISION BTWN A TAXIING CRJ AND A CITATION II WHO HAD TAKEN OFF ON TXWY U AT RIC; VA.

Narrative

FLT FROM RIC TO ZZZ IN CRJ ACFT. WE STARTED AT THE TERMINAL GATE. AFTER CALLING GND FOR TAXI; WE WERE GIVEN 'TXWYS A AND E SHORT OF RWY 2.' GND TOLD US TO SWITCH TO TWR AFTER LEAVING THE RAMP FOR FURTHER INSTRUCTIONS. WE TURNED OFF OF TXWY A ONTO TXWY E AND THAT IS WHEN I NOTICED AN ACFT ON TXWY U FACING NE; TOWARDS US. ALL OF HIS LIGHTS WERE ALREADY ON. WHEN I SAW HIM ACCELERATING; I THOUGHT WE MUST BE APCHING RWY 2. I TURNED TO THE CAPT AND ASKED HIM IF HE WAS GOING TO HOLD SHORT OF RWY 2. HE SAID YES. I THEN POINTED AND SAID 'THERE IS AN AIRPLANE.' THE CAPT STOPPED THE AIRPLANE AND STATED; 'HE JUST TOOK OFF ON A TXWY.' WE REFED OUR CHARTS AGAIN AND CONFIRMED THAT THE OTHER ACFT WAS INDEED NOT ON RWY 2; BUT ON TXWY U WHICH RUNS PARALLEL TO RWY 2. WE HELD OUR POS; OUR NOSE JUST ENCROACHING TXWY U. TWR THEN ADVISED THE ACFT THAT THEY JUST DEPARTED OFF A TXWY. THE TWR THEN CALLED AN ACR ACFT (WHO WAS ON TXWY C SHORT OF RWY 2 ON THE E SIDE) AND STATED THAT IT WAS A GOOD THING THEY WERE NOT CLRED TO CROSS RWY 2. WE THEN CALLED TWR AND ADVISED HIM OF OUR POS AND OUR TAXI INSTRUCTIONS. WE WERE ON TXWY E SHORT OF TXWY U; WE AWAITED FURTHER INSTRUCTIONS AND CONTINUED UNEVENTFULLY. THERE WERE SEVERAL POSITIVE ACTIONS THAT ALLOWED US TO NOTICE THE ACFT IN TIME TO STOP AND AVOID A COLLISION. HAVING STARTED BOTH ENGS AT THE GATE BOTH PLTS WERE LOOKING OUTSIDE AND HAD LITTLE DISTRS. BOTH PLTS HAD OUT TAXI CHARTS AND WERE REFING THEM BEFORE AND DURING TAXI. THE TAXI SPD WAS NOT FAST. CONTRIBUTING FACTORS TO THIS EVENT WERE LOW VISIBILITY; CONTAMINATED TXWY MARKINGS; TWR VISIBILITY AND LACK OF GND TRACKING. HAD THE TWR BEEN ABLE TO SEE THE ACFT'S POS THE ERROR MAY HAVE BEEN CAUGHT PRIOR TO THE TKOF. THE TXWY CONDITIONS MAY HAVE CONTRIBUTED TO THE PLT Y'S PERCEIVED POS.

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.