Narrative:

After completing all checklists; we taxied to the runway. During the taxi out; neither of us noticed any birds in the vicinity of the departure runway or taxiway. Upon completion of the takeoff checklist; we taxied on to the runway to begin the takeoff roll. As the pilot monitoring; my duties were primarily inside the cockpit - monitoring. We began the takeoff roll. Shortly thereafter; PIC called 'birds' followed by 'abort; abort; abort!' as I looked up; I saw a rather large flock of seagulls roosting in the middle of the runway. These seagulls had not been visible to us as we began the takeoff roll. Their coloring and the topography of the runway made them virtually invisible to us. After PIC (pilot in command) correctly executed an aborted takeoff; we taxied back to the ramp to inspect the aircraft. The only visible strike was on the right outboard leading edge of the wing; only blood was visible -- there was no damage to the aircraft. We also visually inspected both engines and determined that no birds had impacted in or near the engines. PIC called the assistant chief pilot on duty who authorized us to continue the flight as planned. Prior to departing; we back-taxied on the runway and enlisted the help of ground personnel from the FBO to ensure that all birds were clear of the area. Both PIC and I believe that there should be notes to all crews that this airport has potentially hazardous bird activity. Pilots should be aware and back-taxi to clear any/all birds prior to departure.

Related reports:

Google
 

Original NASA ASRS Text

Title: CE560 First Officer reports encountering seagulls on the takeoff roll at JKA with the Captain at the controls. The takeoff is rejected and the aircraft returned to the ramp; where no damage is noted. The next takeoff is initiated after back taxiing to clear the runway.

Narrative: After completing all checklists; we taxied to the runway. During the taxi out; neither of us noticed any birds in the vicinity of the departure runway or taxiway. Upon completion of the Takeoff checklist; we taxied on to the runway to begin the takeoff roll. As the pilot monitoring; my duties were primarily inside the cockpit - monitoring. We began the takeoff roll. Shortly thereafter; PIC called 'Birds' followed by 'abort; abort; abort!' As I looked up; I saw a rather large flock of seagulls roosting in the middle of the runway. These seagulls had not been visible to us as we began the takeoff roll. Their coloring and the topography of the runway made them virtually invisible to us. After PIC (pilot in command) correctly executed an aborted takeoff; we taxied back to the ramp to inspect the aircraft. The only visible strike was on the right outboard leading edge of the wing; only blood was visible -- there was no damage to the aircraft. We also visually inspected both engines and determined that no birds had impacted in or near the engines. PIC called the Assistant Chief Pilot on duty who authorized us to continue the flight as planned. Prior to departing; we back-taxied on the runway and enlisted the help of ground personnel from the FBO to ensure that all birds were clear of the area. Both PIC and I believe that there should be notes to all crews that this airport has potentially hazardous bird activity. Pilots should be aware and back-taxi to clear any/all birds prior to departure.

Data retrieved from NASA's ASRS site as of April 2012 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.