B737-300 FLC FAILS TO MAKE A LOGBOOK ENTRY FOR STABILIZER TRIM ANOMALY WHICH CAUSED A REJECTED TKOF.

Date: 2002-12 · Aircraft: B737-300 · Phase: takeoff

Anomalies: aircraft-equipment-problem-less-severe|deviation-discrepancy-procedural-published-material-policy

Synopsis

B737-300 FLC FAILS TO MAKE A LOGBOOK ENTRY FOR STABILIZER TRIM ANOMALY WHICH CAUSED A REJECTED TKOF.

Narrative

WHEN TKOF CLRNC WAS RECEIVED; WE COMPLETED THE BELOW-THE-LINE ITEMS; AND AS THE FO ADVANCED THE PWR THE TKOF WARNING HORN SOUNDED. HE IMMEDIATELY BROUGHT THE PWR TO IDLE AND WE INFORMED THE TWR THAT WE NEEDED TO EXIT THE RWY TO CHK SOME THINGS OUT. WE CYCLED THE SPD BRAKE SEVERAL TIMES TO NO AVAIL; RECYCLED THE FLAPS TO NO AVAIL; AND FINALLY THE STABILIZER TRIM; WHICH DID CLR THE TKOF WARNING. (IT WAS DEFINITELY IN THE GREEN BAND PRIOR TO THIS.) AN UNEVENTFUL FLT FOLLOWED AND I NOTED THE INFO FOR THE IRREGULARITY RPT THAT I WOULD FILL OUT. I DID NOT MAKE A LOGBOOK ENTRY BECAUSE I KNEW (OR THOUGHT I KNEW) THAT A SPD BRAKE RESET WAS THE ONLY 'INFO' WRITE-UP CREWS WERE ALLOWED TO MAKE AND JUST CHALKED UP THE STABILIZER TRIM CORRECTION AS A MOMENTARY GLITCH PROB SOLVED. LATER I FELT THAT THERE WAS ROOM FOR INTERP OF THE FOM AND I BEGAN WONDERING IF I SHOULD HAVE MADE AN 'INFO ONLY' ENTRY FOR THE STABILIZER TRIM; OR IF I SHOULD HAVE MADE A REGULAR MAINT WRITE-UP OR NO WRITE-UP. CONTACTED MAINT TO INFORM THEM THAT THEY MAY WANT TO CHK OUT THE SYS WHEN THE ACFT PASSED THROUGH A MAINT BASE. I SHOULD HAVE TAKEN MY FOM OUT TO HELP CLARIFY THE SIT. ALSO; I WOULD DEFINITELY CONTACT DISPATCH; MAINT; OR A CHIEF PLT FOR ASSISTANCE AND CLARIFICATION. I NEVER FELT RUSHED OR PRESSURED TO GET THE FLT GOING; BUT I WAS 100% SURE THAT NO WRITE-UP WAS REQUIRED. A COUPLE OF EXTRA MINS SPENT DOUBLECHKING WOULD HAVE SAVED A LOT MORE TIME IN THE END.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.