An A300 #2 slat flap computer (sfcc) was meled as giving a false warning. The next flight the #1 and...

Attributes
ACN	934324
Time
Date	201102
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	A300
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Route In Use	Vectors
Flight Plan	IFR
Component
Aircraft Component	Leading Edge Slat
Person 1
Function	First Officer Pilot Flying
Experience	Flight Crew Last 90 Days 50 Flight Crew Total 15000 Flight Crew Type 1200
Person 2
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 25 Flight Crew Total 14000 Flight Crew Type 1500
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural Maintenance Deviation - Procedural MEL

Narrative:

This event started as a reserve call out. I met the captain in the crew room in advance of our flight. The weather was in good shape; and the flight plan looked in order. There was a significant MEL of #2 sfcc (slat flap computer) fault (27-51-01-2). The captain and I reviewed this MEL on the computer in the crew ready room. We proceeded to the aircraft. We preflighted the aircraft; and reviewed the logbook. Aircraft and logbook appeared to be in order. The previous crew inbound had written up the slat issue. Maintenance signed the discrepancy off with the #2 sfcc deferred. We departed and had a normal flight until reaching the landing phase. I was the pilot flying and called for the slats to be extended. They failed to extend. We received a slats system 1 and 2 fault/slats stuck message. We ran the ECAM and the corresponding QRH procedure with no difficulty or issues. The captain declared an emergency with ATC and notified our dispatcher. We proceeded to land on the longest runway. The landing was uneventful. We had the airport rescue and fire fighting team inspect the wheel area for signs of fire and there were none. As a precaution they followed us to the ramp; and once again found no abnormalities. After arrival and all was clear; maintenance inspected the aircraft. I believe that maintenance personnel found problems with multiply slat linkage. I must wonder if the wrong maintenance procedure was applied in our departure airport. I do not know the answer to this question.

Original NASA ASRS Text

Title: An A300 #2 Slat Flap Computer (SFCC) was MELed as giving a false warning. The next flight the #1 and #2 SFCC faults occurred again leading maintenance to believe a slat linkage was faulting. An emergency was declared.

Narrative: This event started as a reserve call out. I met the Captain in the crew room in advance of our flight. The weather was in good shape; and the flight plan looked in order. There was a significant MEL of #2 SFCC (Slat Flap Computer) Fault (27-51-01-2). The Captain and I reviewed this MEL on the computer in the crew ready room. We proceeded to the aircraft. We preflighted the aircraft; and reviewed the logbook. Aircraft and logbook appeared to be in order. The previous crew inbound had written up the slat issue. Maintenance signed the discrepancy off with the #2 SFCC deferred. We departed and had a normal flight until reaching the landing phase. I was the pilot flying and called for the slats to be extended. They failed to extend. We received a Slats System 1 and 2 Fault/Slats stuck message. We ran the ECAM and the corresponding QRH procedure with no difficulty or issues. The Captain declared an emergency with ATC and notified our Dispatcher. We proceeded to land on the longest runway. The landing was uneventful. We had the Airport Rescue and Fire Fighting team inspect the wheel area for signs of fire and there were none. As a precaution they followed us to the ramp; and once again found no abnormalities. After arrival and all was clear; Maintenance inspected the aircraft. I believe that Maintenance personnel found problems with multiply slat linkage. I must wonder if the wrong maintenance procedure was applied in our departure airport. I do not know the answer to this question.

Data retrieved from NASA's ASRS site as of April 2012 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.

An A300 #2 slat flap computer (sfcc) was meled as giving a false warning. The next flight the #1 and #2 sfcc faults occurred again leading maintenance to believe a slat linkage was faulting. An emergency was declared.