A320 flight crew discovers a land ASAP ECAM Memo during climb out. No previous ECAM warnings had been received by the crew but when the recall button was pushed; an Avionics Smoke message is displayed. After some discussion the crew elected to return to the departure airport.

Date: 2011-02 · Aircraft: A320 · Phase: climb

Anomalies: aircraft-equipment-problem-less-severe|flight-deck-cabin-aircraft-event-smoke-fire-fumes-odor

Synopsis

Narrative

After having the number 2 air conditioning pack deferred; we had a normal taxi-out and takeoff. Passing 8;000 FT the Captain and I noticed a Land ASAP (Amber) Memo. There had been no ECAM warning or caution associated with this ECAM Memo. The Captain selected the RCL (recall) button to see if there were any items displayed. Sure enough; there was an Avionics Smoke procedure displayed. There was no perceptible smoke. We asked the Flight Attendants if any indication of smoke in the cabin; and there was none. Both the Captain and I were suspect of this problem; because there didn't appear to be any direct confirmation of the smoke. In addition; the lack of any other ECAM warning or caution made us somewhat suspect of the Land ASAP Memo. The Captain sent a four page ACARS message describing the problem to Maintenance. We also referenced the Flight Manual for further guidance with this particular issue. After further thought; the Captain decided for a return to our departure airport; the closet airport. We informed ATC of our intent to return to our departure airport; and were cleared direct to the airport. We notified Dispatch and the Flight Attendants of our situation. We referenced the overweight landing checklist. We told the flight attendants this would be a normal landing; but did inform them of our indications in the cockpit. After a normal landing; ATC informed us there was no visible smoke. We taxied; parked; and accomplished all required check-list. The Avionics Smoke ECAM message was not displayed after shut-down.

Second reporter narrative

During the climb out I noticed a Message that stated Land ASAP. I pointed it out to the First Officer. We looked at everything to see if we could find a problem. We could see no other indications. No ECAM or other warning lights. I thought it must just be incorrect message. With further investigation; after selecting ECAM recall there was an ECAM for Avionics Smoke. We checked the Flight Manual and it said to follow the ECAM if there was perceptible smoke. There was no smoke; flight attendants perceived no smoke and there were no warning lights. I was sure there was no real problem. In the past I had had this message before and an ECAM engine failure turned up. Well; it was easy to figure out the engine was fine. Not so easy to know if there is smoke in the avionics compartment. I sent some ACARS messages to Maintenance telling them what was happening to see if they had any ideas. We didn't get a response. Originally I thought we would just continue; but then I started feeling more uncomfortable with the situation and told the First Officer that we should return to our departure airport. I asked for a clearance back to our departure airport and notified Dispatch of our plan. Dispatch said our departure airport Operations was notified and we said that as of now the only thing we needed was a mechanic to meet us. We returned to our departure airport with an uneventful landing; except the landing was overweight. We wrote up the overweight landing; but since the rate of decent at touchdown was 100 FT per minute there was no inspection required. There were never any more warning lights and never any smoke. We parked; and our departure airport Operations did a great job of helping us. The mechanic did some computer resets; we refueled; got a new release from Maintenance and Dispatch and left again with no further problems.

More incidents for this aircraft family →

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

← All incident reports Global safety overview