Narrative:

On postflt inspection after arrival at sna, discovered evidence of bird strike on the #1 engine. I immediately radioed company operations and talked to the gate agent. I then made a phone call to company maintenance control in sea. When I returned to the airplane I met with the contract mechanic at the #1 engine. The crew at that time was informed that company had another inbound flight and that we were to remove our belongings from the airplane, as it was about to be towed from the gate to remote parking. I then called crew scheduling to see what they planned for us. I also answered a phone call from sna airport operations and let them know that we believed the bird strike occurred on takeoff from oak and not at sna. Shortly thereafter I was informed by operations that company mechanics were driving from lax to come and fix the airplane and then was told to deadhead home to sea by crew scheduling. After the 'dust had settled,' as we were riding home, I realized as PIC I had not entered the discrepancy in the maintenance logbook, primarily due to the break of routine of the airplane being towed from the gate, with the logbook in the airplane. Upon landing at home base I again called maintenance control to ensure my observations were recorded. Although it is very unlikely that another crew would have been assigned the airplane, I still should have logged it first to ensure the damage not being overlooked.

Related reports:

Google
 

Original NASA ASRS Text

Title: CAPT OF A B737-400 FOUND DAMAGE TO THE #1 ENG DURING POSTFLT INSPECTION CAUSED BY A BIRD STRIKE DURING DEP AND CONTACTED COMPANY MAINT FOR INSPECTION AND SUBSEQUENT GROUNDING OF THE ACFT. HOWEVER, HE FORGOT TO MAKE A WRITE-UP IN THE ACFT LOGBOOK BEFORE LEAVING THE ACFT.

Narrative: ON POSTFLT INSPECTION AFTER ARR AT SNA, DISCOVERED EVIDENCE OF BIRD STRIKE ON THE #1 ENG. I IMMEDIATELY RADIOED COMPANY OPS AND TALKED TO THE GATE AGENT. I THEN MADE A PHONE CALL TO COMPANY MAINT CTL IN SEA. WHEN I RETURNED TO THE AIRPLANE I MET WITH THE CONTRACT MECH AT THE #1 ENG. THE CREW AT THAT TIME WAS INFORMED THAT COMPANY HAD ANOTHER INBOUND FLT AND THAT WE WERE TO REMOVE OUR BELONGINGS FROM THE AIRPLANE, AS IT WAS ABOUT TO BE TOWED FROM THE GATE TO REMOTE PARKING. I THEN CALLED CREW SCHEDULING TO SEE WHAT THEY PLANNED FOR US. I ALSO ANSWERED A PHONE CALL FROM SNA ARPT OPS AND LET THEM KNOW THAT WE BELIEVED THE BIRD STRIKE OCCURRED ON TKOF FROM OAK AND NOT AT SNA. SHORTLY THEREAFTER I WAS INFORMED BY OPS THAT COMPANY MECHS WERE DRIVING FROM LAX TO COME AND FIX THE AIRPLANE AND THEN WAS TOLD TO DEADHEAD HOME TO SEA BY CREW SCHEDULING. AFTER THE 'DUST HAD SETTLED,' AS WE WERE RIDING HOME, I REALIZED AS PIC I HAD NOT ENTERED THE DISCREPANCY IN THE MAINT LOGBOOK, PRIMARILY DUE TO THE BREAK OF ROUTINE OF THE AIRPLANE BEING TOWED FROM THE GATE, WITH THE LOGBOOK IN THE AIRPLANE. UPON LNDG AT HOME BASE I AGAIN CALLED MAINT CTL TO ENSURE MY OBSERVATIONS WERE RECORDED. ALTHOUGH IT IS VERY UNLIKELY THAT ANOTHER CREW WOULD HAVE BEEN ASSIGNED THE AIRPLANE, I STILL SHOULD HAVE LOGGED IT FIRST TO ENSURE THE DAMAGE NOT BEING OVERLOOKED.

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