Narrative:

While taxiing to runway on taxiway a an air carrier airlines B727 had the #2 engine shut down. The air carrier airbus was following at safe distance. The B727 stopped and when he tried to resume movement the boeing would not move without excessive power on the #1 and #3 engines. The B727 air carrier crew started the #2 engine. When power was applied the airbus was definitely subjected to excessive engine thrust. An ECAM warning appeared on the airbus east/west monitor. F/control law was the warning. I discussed the warning with the first officer and we decided the problem would be corrected as soon as we got airflow over the aircraft on takeoff roll. We tried to reset both elevator/aileron computers with no success. The problem did not reset on takeoff. We complied with the non normal procedures and the problem reset itself while we taxied to the gate in dca. I wrote the occurrence in the maintenance log and the mechanics did a system check that showed the problem had occurred and had reset itself. Next time I will return to the gate and have the mechanics reset the problem before takeoff. Live and learn.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN A320 FLC DEPARTS FOR DEST ARPT AFTER THEY ARE UNABLE TO CLR THE ECAM WARNING OF THE MESSAGE, 'F SLANT CTL LAW' WHICH CAME ON AFTER AN ENCOUNTER WITH JET BLAST ON THE GND AT LGA, NY.

Narrative: WHILE TAXIING TO RWY ON TXWY A AN ACR AIRLINES B727 HAD THE #2 ENG SHUT DOWN. THE ACR AIRBUS WAS FOLLOWING AT SAFE DISTANCE. THE B727 STOPPED AND WHEN HE TRIED TO RESUME MOVEMENT THE BOEING WOULD NOT MOVE WITHOUT EXCESSIVE PWR ON THE #1 AND #3 ENGS. THE B727 ACR CREW STARTED THE #2 ENG. WHEN PWR WAS APPLIED THE AIRBUS WAS DEFINITELY SUBJECTED TO EXCESSIVE ENG THRUST. AN ECAM WARNING APPEARED ON THE AIRBUS E/W MONITOR. F/CTL LAW WAS THE WARNING. I DISCUSSED THE WARNING WITH THE FO AND WE DECIDED THE PROB WOULD BE CORRECTED AS SOON AS WE GOT AIRFLOW OVER THE ACFT ON TKOF ROLL. WE TRIED TO RESET BOTH ELEVATOR/AILERON COMPUTERS WITH NO SUCCESS. THE PROB DID NOT RESET ON TKOF. WE COMPLIED WITH THE NON NORMAL PROCS AND THE PROB RESET ITSELF WHILE WE TAXIED TO THE GATE IN DCA. I WROTE THE OCCURRENCE IN THE MAINT LOG AND THE MECHS DID A SYS CHK THAT SHOWED THE PROB HAD OCCURRED AND HAD RESET ITSELF. NEXT TIME I WILL RETURN TO THE GATE AND HAVE THE MECHS RESET THE PROB BEFORE TKOF. LIVE AND LEARN.

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.