Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 107; Flight Crew Total 20000; Flight Crew Type 5000
Ground Event / Encounter Person / Animal / Bird
Flight Crew Rejected Takeoff; Flight Crew Returned To Gate; General Flight Cancelled / Delayed; General Maintenance Action
Environment - Non Weather Related
There were no bird or wildlife reports from ATC or preceding aircraft. Upon a seemingly normal takeoff roll; soon after 100 knots and well prior to V1 we observed large bird take off from the runway (just right of centerline about 150 feet ahead of us) we anticipated a thump from a possible impact of the bird but instead we heard a very loud bang (compressor stall) MUCH louder than an impact of a large bird.  Suspecting possible engine damage associated with the loud bang I rejected the takeoff at 135 knots at 365;000 pounds (planned V speeds; V1 148; Vr 159; V2 164). We called ATC to advise of our situation. We decelerated and exited/cleared the runway and followed procedures and checklists. We observed BTMS numbers of 2's and 4's as we stopped.Completing QRH items; I started the APU and as [ground personnel] approached we observed the BTMS numbers increasing to maximum values of 8's and 9's. When we made interphone contact with the [ground personnel] he advised us that as they approached the aircraft there was some smoke coming from the left brakes and his men had already placed several cooling fans around the aircraft and that the smoking brakes had stopped. He also advised us that the brake temps were reading over 500 degrees from his infrared readings. We advised him not to approach the brakes/tires due to burst possibility and we shut down both engines but left flaps at takeoff position as per QRH. We consulted the RTO brake cooling charts; hot brakes checklists/charts and determined that we were in the Warning zone and calculated an 80 minute cooling time.  We conferred with the flight attendants and verified that the cabin situation was calm and stable. They reported that several passengers observed a burst of flame from the right engine associated with the bird strike. Also an outbound; taxiing aircraft observed/reported the flash of flame from our right engine. (Confirming my suspicions of possible wildlife ingestion) We consulted with Dispatch; Maintenance Control and the [Operations Manager] via SATCOM several times to coordinate and establish appropriate/best options. While we waited out our cooling time; officials took photos and samples of bird remains from our aircraft. We were informed that we had struck not one; but two large birds. We coordinated with OPS and apron control for a gate/hard stand. As our 80 minute cooling time concluded (BTMS values of 1 and 2) we asked contract maintenance to confirm that the fuse plugs had not melted prior to movement. Making timely and appropriate PA's; we coordinated with the FA's (Flight Attendants); we retracted the flaps when clear; we were towed to the hard stand and eventually deplaned. Either the wildlife officials or contract maintenance cleaned all of the blood and feathers from the nacelle and fan before we left the cooling location.  I saw a photo from one of the mechanics and the bloody impact was at the 6 o'clock position centered on the leading edge of the engine lip. About 2 feet wide left and right and about 6 inches toward the inside and about 12 inches along the underside of the nacelle. When we finally were able to exit the airplane; very little evidence remained but upon our post incident walk around and engine inspection. We noted a small amount of wildlife remains on the fan hub; fan shroud; bypass stators and engine compressor inlet.I say 'WE' in most of my narrative because it was genuinely a team effort and I have a great team every time I fly. FO (First Officer) and IRO (International Relief Officer) were exemplary in the performance of their duties and they were an incredible asset during all aspects of this incident. We as a team; made a dozen or so PA's to the passengers; we coordinated and maintained a dialog with the flight attendants; answered multiple simultaneous queries and communications to/from ATC; Police; Ops; Local Maintenance; Dispatch; [Maintenance Control] and [Operations Management] in addition to performing QRH; checklist; FOM; and SOP tasks. The flight attendants did an exemplary job of controlling the cabin; comforting the passengers and providing input to the flight deck.I will speak for the entire crew in that we all feel that we well prepared professionally for this type of event and although the coordination/support of all involved created some communication challenges; we are thankful for such support.
During the takeoff run; at approximately 135 knots [V1-148]; I saw and stated 'bird' ahead of us just right of centerline. I saw the bird start to fly away as we were abeam it. Shortly after that we heard a very loud sound from the right side of the airplane. A reject was annunciated and the appropriate procedures applied. I called Tower and let them know what we were doing. The IRO (International Relief Officer) made a cabin announcement. We exited the high speed taxiway and came to a stop on the parallel taxiway. Tower informed us that they observed a large flame exit the right engine on our takeoff roll. A passenger and a pilot on another aircraft also verified the flame exiting the right engine on takeoff roll. We accomplished the rejected takeoff checklist and also calculated our brake cooling time from the appropriate checklist. 80 minutes was our conclusion. Cooling fans were set up after [ground personnel] informed us that the left brakes were smoking. Dispatch; [Maintenance Control]; and the [Operations Manager] were all called and informed of the situation. After the allotted cooling times and confirmation that the brakes had cooled sufficiently; we were towed back to our original parking spot. Passengers were offloaded.
B767 flight crew reported rejecting the takeoff following a bird strike in the right engine that resulted in a compressor stall.