B777-300 Captain reported a CAS 'smoke Detect' message during cruise. After a cabin search no smoke was identified. Flight crew conferred with Dispatch and Maintenance and elected to continue to destination. Flight landed safely.
Synopsis
B777-300 Captain reported a CAS 'smoke Detect' message during cruise. After a cabin search no smoke was identified. Flight crew conferred with Dispatch and Maintenance and elected to continue to destination. Flight landed safely.
Narrative
At cruise after initial level off at FL320; all pages of all flight attendant Flight Safety Organization screens had Smoke Detect in red in the bottom left hand corner of the screen. No location was identified. We searched the plane for any signs of smoke; none was found anywhere; lavs; rest areas; etc. While the flight attendants continued to be alert; the cockpit crew called Dispatch and were patched through to the Chief Pilot and Operations. No one had heard of a Smoke Detect without a location. Making the situation more complex was the fact that we had lithium ion batteries in the bulk cargo along with acetone; two separate DG shipments. We also had a forward cargo fan deferred. It was decided that if we could not reset the Smoke Detect message to confirm if it was still active; we would divert to ZZZ. If there was indeed smoke detected; we were diverting to ZZZ1. At no point was smoke detected by the Flight Attendants. Operations offered a technique to reset the Flight Safety Organization panel; but it only reset the lighting and cabin temperature aspects of the system; it did not remove the smoke detect message from the screen.The flight attendants were fantastic throughout the event. We had three brand new flight attendants; the Purser has been working for [the] Company for 2 months. He handled the situation quite well. Name was particularly helpful. He researched the problem and found a reset in the manual. His problem was that the manual did not describe the location of the buttons suggested in the reset. He continued to search the cabin and found the buttons referenced at door 1R. I asked him to proceed with the reset procedure he found in his manual and the Smoke Detect message was cleared from all screens. The message did not reappear. Dispatch; the Chief Pilot; and Operations all agreed the situation was resolved and the flight continued to ZZZ2. The entire crew agreed and we continued uneventfully.All crew worked extremely well together; CRM was used throughout the entire event which lasted more than an hour. Name and Name 1 really saved the day on this one.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.