Narrative:

CAT 3 at ZZZ runway 34R. Wind 050/25. Within limits for crosswind autoland. Airplane did fine on the approach. All callouts were made and all FMA's were there. Upon landing, airplane kicked out crab dropped right wing very nicely. Then it hit so hard we bounced up in the air only to be blown off to the left of the runway. The airplane then landed nose first and headed for the right side of the runway. We were using autobrakes medium and the brakes kicked in fine. I tried steering the plane back to centerline as we were about to go off the right side of the runway. We taxied to the gate and wrote up unsat autoland. The mechanic pulled a post flight report of the ACARS and said, 'did you guys know that a autoplt was disconnected and you lost an elac 1 three mins before landing?' the ACARS showed elac 1 and autoplt flight ap off at XA33Z, three mins before landing. Callback conversation with reporter revealed the following information: the reporter stated no ECAM status messages were displayed prior to arming the autoplts and during the approach the flight mode annunciator indicated CAT 3, dual autoplt engagement and MDA data. The reporter said at 400 feet AGL the 'land' mode was engaged and indicated on the flight mode annunciator. The reporter stated the airplane had to have been in autoland with both autoplts engaged as it made the crosswind landing with a crab and right wing down and this can only be accomplished with two autoplts engaged. The reporter said at no time during the approach and landing was any equipment failure noted. The reporter stated the possibility of elevator aileron computer failure on landing. The reporter said engineering believes that is the only good explanation for this event and the clock that timed all the events was in error.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN AIRBUS 320 IN AUTOLAND MODE LNDG KICKED OUT CRAB AND DROPPED R WING THEN HIT HARD BOUNCING BACK INTO AIR THEN LANDED NOSE FIRST. A POST FLT CHECK REVEALED ELAC #1 FAILED 3 MINS PRIOR TO LNDG.

Narrative: CAT 3 AT ZZZ RWY 34R. WIND 050/25. WITHIN LIMITS FOR XWIND AUTOLAND. AIRPLANE DID FINE ON THE APCH. ALL CALLOUTS WERE MADE AND ALL FMA'S WERE THERE. UPON LNDG, AIRPLANE KICKED OUT CRAB DROPPED R WING VERY NICELY. THEN IT HIT SO HARD WE BOUNCED UP IN THE AIR ONLY TO BE BLOWN OFF TO THE L OF THE RWY. THE AIRPLANE THEN LANDED NOSE FIRST AND HEADED FOR THE R SIDE OF THE RWY. WE WERE USING AUTOBRAKES MEDIUM AND THE BRAKES KICKED IN FINE. I TRIED STEERING THE PLANE BACK TO CTRLINE AS WE WERE ABOUT TO GO OFF THE R SIDE OF THE RWY. WE TAXIED TO THE GATE AND WROTE UP UNSAT AUTOLAND. THE MECHANIC PULLED A POST FLT RPT OF THE ACARS AND SAID, 'DID YOU GUYS KNOW THAT A AUTOPLT WAS DISCONNECTED AND YOU LOST AN ELAC 1 THREE MINS BEFORE LNDG?' THE ACARS SHOWED ELAC 1 AND AUTOPLT FLT AP OFF AT XA33Z, THREE MINS BEFORE LNDG. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED NO ECAM STATUS MESSAGES WERE DISPLAYED PRIOR TO ARMING THE AUTOPLTS AND DURING THE APCH THE FLT MODE ANNUNCIATOR INDICATED CAT 3, DUAL AUTOPLT ENGAGEMENT AND MDA DATA. THE RPTR SAID AT 400 FEET AGL THE 'LAND' MODE WAS ENGAGED AND INDICATED ON THE FLT MODE ANNUNCIATOR. THE RPTR STATED THE AIRPLANE HAD TO HAVE BEEN IN AUTOLAND WITH BOTH AUTOPLTS ENGAGED AS IT MADE THE XWIND LNDG WITH A CRAB AND R WING DOWN AND THIS CAN ONLY BE ACCOMPLISHED WITH TWO AUTOPLTS ENGAGED. THE RPTR SAID AT NO TIME DURING THE APCH AND LNDG WAS ANY EQUIP FAILURE NOTED. THE RPTR STATED THE POSSIBILITY OF ELEVATOR AILERON COMPUTER FAILURE ON LNDG. THE RPTR SAID ENGINEERING BELIEVES THAT IS THE ONLY GOOD EXPLANATION FOR THIS EVENT AND THE CLOCK THAT TIMED ALL THE EVENTS WAS IN ERROR.

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.