20250104004852I

Incident · Minor damage

FAA incident report · Gulfstream Aerospace GVII-G500 · Dulles, VA · January 4, 2025

Date
January 4, 2025 · 15:28 local
Place
Dulles, VA
Airport
Washington Dulles International
Phase of flight
Ground/Ramp/Ma
Operating rules
Air taxi and commuter (Part 135)
Operator
KKVA
Collision
Collision on the ground
Damage
Minor damage
Aircraft
N222NB
Reported as
Gulfstream Aerospace GVII-G500
Reported engine
Pratt & Whitney Canada PW814GA
People aboard
7
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Airline transport, flight instructor
Pilot’s flight hours
12,612 total392 in this make and model81 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

While aircraft #1 was taxiing for departure on the ramp, the right wing struck aircraft #2 (aircraft #2 was parked and not moving) causing damage to the aircraft #2 tailcone.

The fixed based operator (FBO) director stated that "aircraft #1 initially attempted to exit the ramp via Z2 but encountered an inbound aircraft planning to utilize the same. At the time of the incident, aircraft #1 was not in contact with the FBO, and was proceeding on our ramp without the aid of a marshaller or wing spotter’s when the incident occurred. Upon encountering the inbound aircraft, aircraft #1 turned slightly to the right in an attempt to allow the oncoming aircraft to pass, but a short time thereafter proceeded to make a right hand turn to the north and attempted to taxi between 2 rows of parked aircraft striking aircraft #2 and no other aircraft. They proceeded to exit the ramp at Z1 and upon realizing they’d struck an aircraft then established communications on our arinc frequency requesting to return to our ramp and were parked in the very same location they had departed from. There was no further damage to any other aircraft, nor any injuries to any ground personnel. There was no other property damage as a result of this incident."

The pilot in command of aircraft #1 provided the following statement "we were cleared to taxi from the ramp to runway 30, but told to give way to an inbound citation. We were unable to get any marshallers on the ramp since privacy data omitted was very short staffed that day. We were facing away from the taxi way so we turned to the right so we could see, and wait for the inbound citation. I noticed that the citation was entering the ramp at Z2 which is the normal exit. We taxied further to the right to allow him room to enter the ramp. However, the citation didn't move and continued to block the Z2 exit. We decided to try and exit the ramp at Z1 which required us to taxi between 2 rows of parked planes. I was the pm and thought we were clear of aircraft #2 on our right side. I let the flying pilot know this and we proceeded. We both felt a bump and thought we had hit a pothole on the ramp. We continued to exit at Z1 and made a left turn to join z taxi way. At this time the pilot flying noticed the piece of tail cone from aircraft #2 on the ramp. We realized that was what the bump was. We requested taxi clearance back onto the atlantic ramp and reported the incident."

As the FAA filed it

WHILE AIRCRAFT #1 WAS TAXIING FOR DEPARTURE ON THE RAMP, THE RIGHT WING STRUCK AIRCRAFT #2 (AIRCRAFT #2 WAS PARKED AND NOT MOVING) CAUSING DAMAGE TO THE AIRCRAFT #2 TAILCONE.

THE FIXED BASED OPERATOR (FBO) DIRECTOR STATED THAT "AIRCRAFT #1 INITIALLY ATTEMPTED TO EXIT THE RAMP VIA Z2 BUT ENCOUNTERED AN INBOUND AIRCRAFT PLANNING TO UTILIZE THE SAME. AT THE TIME OF THE INCIDENT, AIRCRAFT #1 WAS NOT IN CONTACT WITH THE FBO, AND WAS PROCEEDING ON OUR RAMP WITHOUT THE AID OF A MARSHALLER OR WING SPOTTER’S WHEN THE INCIDENT OCCURRED. UPON ENCOUNTERING THE INBOUND AIRCRAFT, AIRCRAFT #1 TURNED SLIGHTLY TO THE RIGHT IN AN ATTEMPT TO ALLOW THE ONCOMING AIRCRAFT TO PASS, BUT A SHORT TIME THEREAFTER PROCEEDED TO MAKE A RIGHT HAND TURN TO THE NORTH AND ATTEMPTED TO TAXI BETWEEN 2 ROWS OF PARKED AIRCRAFT STRIKING AIRCRAFT #2 AND NO OTHER AIRCRAFT. THEY PROCEEDED TO EXIT THE RAMP AT Z1 AND UPON REALIZING THEY’D STRUCK AN AIRCRAFT THEN ESTABLISHED COMMUNICATIONS ON OUR ARINC FREQUENCY REQUESTING TO RETURN TO OUR RAMP AND WERE PARKED IN THE VERY SAME LOCATION THEY HAD DEPARTED FROM. THERE WAS NO FURTHER DAMAGE TO ANY OTHER AIRCRAFT, NOR ANY INJURIES TO ANY GROUND PERSONNEL. THERE WAS NO OTHER PROPERTY DAMAGE AS A RESULT OF THIS INCIDENT."

THE PILOT IN COMMAND OF AIRCRAFT #1 PROVIDED THE FOLLOWING STATEMENT "WE WERE CLEARED TO TAXI FROM THE RAMP TO RUNWAY 30, BUT TOLD TO GIVE WAY TO AN INBOUND CITATION. WE WERE UNABLE TO GET ANY MARSHALLERS ON THE RAMP SINCE ^PRIVACY DATA OMITTED^ WAS VERY SHORT STAFFED THAT DAY. WE WERE FACING AWAY FROM THE TAXI WAY SO WE TURNED TO THE RIGHT SO WE COULD SEE, AND WAIT FOR THE INBOUND CITATION. I NOTICED THAT THE CITATION WAS ENTERING THE RAMP AT Z2 WHICH IS THE NORMAL EXIT. WE TAXIED FURTHER TO THE RIGHT TO ALLOW HIM ROOM TO ENTER THE RAMP. HOWEVER, THE CITATION DIDN'T MOVE AND CONTINUED TO BLOCK THE Z2 EXIT. WE DECIDED TO TRY AND EXIT THE RAMP AT Z1 WHICH REQUIRED US TO TAXI BETWEEN 2 ROWS OF PARKED PLANES. I WAS THE PM AND THOUGHT WE WERE CLEAR OF AIRCRAFT #2 ON OUR RIGHT SIDE. I LET THE FLYING PILOT KNOW THIS AND WE PROCEEDED. WE BOTH FELT A BUMP AND THOUGHT WE HAD HIT A POTHOLE ON THE RAMP. WE CONTINUED TO EXIT AT Z1 AND MADE A LEFT TURN TO JOIN Z TAXI WAY. AT THIS TIME THE PILOT FLYING NOTICED THE PIECE OF TAIL CONE FROM AIRCRAFT #2 ON THE RAMP. WE REALIZED THAT WAS WHAT THE BUMP WAS. WE REQUESTED TAXI CLEARANCE BACK ONTO THE ATLANTIC RAMP AND REPORTED THE INCIDENT."

Other aircraft in the event · 1

Each aircraft in a collision has its own report.

LX-AMBBombardier CL-600-2B16No report for this aircraft in the release