Narrative:

We taxied to runway 13R in ZZZ. Reaching the end of the runway, tower cleared us for an immediate takeoff, referencing company on a 3 1/2 mi final. We proceeded to accomplish the below-the-line items and discovered we had a fwd-entry light on the overhead panel. With company on such a short final behind us, I elected to taxi clear of the runway. The first officer told tower that we needed to taxi clear of the runway. Tower asked if we needed any assistance. We answered no. Clear of the runway, I called the 'a' flight attendant to recycle the door. The 'a' flight attendant stated that the handle looked to be up a little. After she recycled the handle, the forward-entry light went out, and we departed without further event. The problem I have with this event is on the way to ZZZ2, while airborne, I got to talking with a captain that was on the jumpseat commuting to ZZZ2. I knew that the event was going to require an incident report. But as we got to talking, we discussed a logbook entry, and whether or not the event would require a logbook entry for the rejected takeoff. I should have pulled out the fom and looked it up, but I was sure that it did. I remembered having a long discussion in upgrade class about rejected takeoff and how the FAA was tracking then, and about aborted takeoffs and information write-ups. I remembered that the gist of our discussion was that if you are cleared for takeoff or have crossed the hold-short line and have to exit the runway for any reason, incident report is required. In this case, I got incident report and logbook entry switched. Since it was the first time for me to make such a write-up, I should have pulled out the fom and referenced it prior to writing in the logbook. But, I was so sure that I was correct in making an information write-up referencing a very, very low speed abort (I really do not believe you could even call it an abort. We were at a new captain taxi speed) and so I did. In ZZZ1, I called and spoke to chief pilot to make sure what I had done was correct and followed the letter of the law. Well, I soon found out that what I had done was not correct. Chief advised me to mark out the write-up and write 'entered in error employee number incident report filed,' so I did. I know that the only information write-up we do is for a takeoff warning horn. Why I talked myself into doing it for this, I do not know. I have since re-read the fom referencing information write-ups and the whole logbook chapter. I have learned that prior to putting pen to paper, if there is any question about what I am doing, especially if time is of the essence, it is really easy to make a simple phone call to save oneself a lot of trouble and embarrassment in the future.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-200 MADE A LOW SPD REJECTED TKOF DUE TO DOOR WARNING. ENTERED IN LOGBOOK IN ERROR AS INFO RPT.

Narrative: WE TAXIED TO RWY 13R IN ZZZ. REACHING THE END OF THE RWY, TWR CLRED US FOR AN IMMEDIATE TKOF, REFING COMPANY ON A 3 1/2 MI FINAL. WE PROCEEDED TO ACCOMPLISH THE BELOW-THE-LINE ITEMS AND DISCOVERED WE HAD A FWD-ENTRY LIGHT ON THE OVERHEAD PANEL. WITH COMPANY ON SUCH A SHORT FINAL BEHIND US, I ELECTED TO TAXI CLR OF THE RWY. THE FO TOLD TWR THAT WE NEEDED TO TAXI CLR OF THE RWY. TWR ASKED IF WE NEEDED ANY ASSISTANCE. WE ANSWERED NO. CLR OF THE RWY, I CALLED THE 'A' FLT ATTENDANT TO RECYCLE THE DOOR. THE 'A' FLT ATTENDANT STATED THAT THE HANDLE LOOKED TO BE UP A LITTLE. AFTER SHE RECYCLED THE HANDLE, THE FORWARD-ENTRY LIGHT WENT OUT, AND WE DEPARTED WITHOUT FURTHER EVENT. THE PROB I HAVE WITH THIS EVENT IS ON THE WAY TO ZZZ2, WHILE AIRBORNE, I GOT TO TALKING WITH A CAPT THAT WAS ON THE JUMPSEAT COMMUTING TO ZZZ2. I KNEW THAT THE EVENT WAS GOING TO REQUIRE AN INCIDENT RPT. BUT AS WE GOT TO TALKING, WE DISCUSSED A LOGBOOK ENTRY, AND WHETHER OR NOT THE EVENT WOULD REQUIRE A LOGBOOK ENTRY FOR THE REJECTED TKOF. I SHOULD HAVE PULLED OUT THE FOM AND LOOKED IT UP, BUT I WAS SURE THAT IT DID. I REMEMBERED HAVING A LONG DISCUSSION IN UPGRADE CLASS ABOUT REJECTED TKOF AND HOW THE FAA WAS TRACKING THEN, AND ABOUT ABORTED TKOFS AND INFO WRITE-UPS. I REMEMBERED THAT THE GIST OF OUR DISCUSSION WAS THAT IF YOU ARE CLRED FOR TKOF OR HAVE CROSSED THE HOLD-SHORT LINE AND HAVE TO EXIT THE RWY FOR ANY REASON, INCIDENT RPT IS REQUIRED. IN THIS CASE, I GOT INCIDENT RPT AND LOGBOOK ENTRY SWITCHED. SINCE IT WAS THE FIRST TIME FOR ME TO MAKE SUCH A WRITE-UP, I SHOULD HAVE PULLED OUT THE FOM AND REFED IT PRIOR TO WRITING IN THE LOGBOOK. BUT, I WAS SO SURE THAT I WAS CORRECT IN MAKING AN INFO WRITE-UP REFING A VERY, VERY LOW SPD ABORT (I REALLY DO NOT BELIEVE YOU COULD EVEN CALL IT AN ABORT. WE WERE AT A NEW CAPT TAXI SPD) AND SO I DID. IN ZZZ1, I CALLED AND SPOKE TO CHIEF PLT TO MAKE SURE WHAT I HAD DONE WAS CORRECT AND FOLLOWED THE LETTER OF THE LAW. WELL, I SOON FOUND OUT THAT WHAT I HAD DONE WAS NOT CORRECT. CHIEF ADVISED ME TO MARK OUT THE WRITE-UP AND WRITE 'ENTERED IN ERROR EMPLOYEE NUMBER INCIDENT RPT FILED,' SO I DID. I KNOW THAT THE ONLY INFO WRITE-UP WE DO IS FOR A TKOF WARNING HORN. WHY I TALKED MYSELF INTO DOING IT FOR THIS, I DO NOT KNOW. I HAVE SINCE RE-READ THE FOM REFING INFO WRITE-UPS AND THE WHOLE LOGBOOK CHAPTER. I HAVE LEARNED THAT PRIOR TO PUTTING PEN TO PAPER, IF THERE IS ANY QUESTION ABOUT WHAT I AM DOING, ESPECIALLY IF TIME IS OF THE ESSENCE, IT IS REALLY EASY TO MAKE A SIMPLE PHONE CALL TO SAVE ONESELF A LOT OF TROUBLE AND EMBARRASSMENT IN THE FUTURE.

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.