Singapore Airlines flight SQ368 was operated with a Boeing 777-300ER registered 9V-SWB that departed from Singapore Changi Airport at 0224 hrs for Milan Malpensa on 27 June 2016.

The aircraft carried two sets of operating crew, i.e. four pilots in total.

Singapore Airlines introduced a similar design on board the Boeing 777 aircraft through its ongoing cabin retrofit program. The Boeing 777-300 was the first model to undergo refit and had introduced the product on the Singapore–Sydney route on 22 July 2009. Read user reviews for Singapore Airlines Boeing 777-200ER (772) Layout 2. Submitted by Jc E on 2018/11/29 for Seat 5a. Flew from sin-hkg but was really odd business class because it wasn't really flat bed it was like a little cubby for your feet and you had to lie diagonally definately not as good as american, cathay, turkish, emirates.

As Singapore Airlines flight SQ368 was climbing to its cruising altitude, the flight crew encountered weather which required them to perform weather avoidance manoeuvers. About 30 minutes into the flight, when the aircraft had climbed to 30,000 feet, the flight crew noticed that the oil quantity parameter in the Engine Indicating and Crew Alerting System (EICAS) showed 17 units for the left engine but only 1 unit for the right engine.

watch the video …

The flight crew also noticed from the EICAS display that the right engine oil pressure was fluctuating between 65 and 70 psi while the oil temperature for the right engine was 10°C higher than the left engine. However, both the oil pressure and temperature parameters were within the normal operating range.

The flight crew of Singapore Airlines flight SQ368 looked through their available manuals but was unable to find an appropriate procedure that addressed the low engine oil quantity situation.

At 0304 hrs, the Pilot-in-command (PIC) of Singapore Airlines flight SQ368 contacted their company’s engineering control centre for assistance via satellite communication (SATCOM). The PIC informed the engineer on duty of the engine parameters and asked if it was safe to continue with the flight. The engineer informed the PIC that since the oil pressure was within the normal operating range, there could be a faulty oil quantity indication. The engineer advised the PIC to continue with the flight but monitor the right engine oil parameters. The engineer told the PIC that he would also contact the company’s technical services personnel for advice.

After being briefed by the engineer on the situation, the technical services personnel believed that the problem with Singapore Airlines flight SQ368 was a faulty oil quantity indication.

As the aircraft had just departed and was not far from Singapore, the technical services personnel recommended that the aircraft return to Singapore.

According to the flight crew, as they were passing waypoint VPG at approximately 0320 hrs, the First Officer performed a routine fuel quantity check. After comparing the TOTALIZER fuel quantity with the planned fuel remaining quantity, it was determined that the fuel consumption was better than expected as the fuel on board was 600 kg more than the expected value.

At 0328 hrs, the engineer sent a message via the Aircraft Communication and Reporting System (ACARS) to the flight crew of Singapore Airlines flight SQ368 informing them about the recommendation by the technical services personnel for the aircraft to return to Singapore and requesting them to contact the engineering control centre.

The PIC contacted the engineering control centre and a conference call among the PIC, the engineering control centre and the technical services personnel was held, which lasted for about 20 minutes. The PIC informed the rest that the flight crew had been monitoring the right engine oil parameters for 50 minutes and other than the indicated low oil quantity, the parameters appeared normal. It was jointly assessed that the flight could continue to Milan with the proviso that the flight crew monitor the right engine oil parameters and contact the engineering control centre for assistance if needed.

Singapore Airlines Boeing 777 300er

Shortly after the conference call ended, the flight crew of Singapore Airlines flight SQ368 felt an unusual vibration in the control column and cockpit floor.

The flight crew tried to diagnose the problem by changing the engine power settings and found that the vibration disappeared when the power of the right engine was reduced. At about the same time, the flight crew caught a momentary wisp of burnt smell in the cockpit but the smell disappeared quickly.

At 0404 hrs, the PIC of Singapore Airlines flight SQ368 informed the engineering control centre about the vibrations which the flight crew experienced whenever the right engine was operated at higher power settings. In the ensuing conference call among the PIC, the engineering control centre and the technical services personnel, it was assessed that there was no need to shut down the right engine and decided that the aircraft would return to Singapore with the right engine operating at idle power. In the midst of the conference call, the In-flight supervisor (IFS) informed the flight crew that there was a burnt smell detected in the cabin. In response, the flight crew turned off the right engine bleed system.

According to the cabin crew, the smell was particularly strong in the business class cabin, in the forward part of the aircraft. The cabin crew distributed wet towels for the passengers to hold over their nose and breathe through it.

After the conference call ended, the flight crew reduced the right engine to idle power and proceeded to turn the aircraft around to return to Singapore. For the return journey to Singapore, the flight crew adopted the procedure for single engine operation, including a descent to 17,000 feet before reducing the right engine to idle power.

When the IFS informed the flight crew that the burnt smell in the cabin was still present, the right air conditioning pack and recirculating fans were switched off. Shortly after, the smell in the cabin subsided.

At 0521 hrs, the flight crew of Singapore Airlines flight SQ368 received a FUEL DISAGREE message on the EICAS. The flight crew performed the FUEL DISAGREE checklist. The FUEL DISAGREE checklist suggested four scenarios in which a fuel leak should be suspected and when the flight crew should perform the FUEL LEAK checklist. One such scenario is when the TOTALIZER fuel quantity is less than the CALCULATED fuel quantity.

The flight crew observed from the display of the flight management system that TOTALIZER fuel quantity was about 79 tonnes and the CALCULATED fuel quantity was about 83 tonnes.

However, the flight crew did not perform the FUEL LEAK checklist. According to the flight crew, they believed the CALCULATED fuel quantity was no longer accurate in view of the following:

• Input changes had been made to the flight management system after the right engine was set to idle power.
• They were no longer on the planned flight route.
• They had 600 kg more fuel than expected when they last performed a routine fuel check .

Thus, the flight crew performed their own fuel calculation by subtracting the amount of fuel consumed from the total amount of fuel at the start of the flight. The fuel consumed was calculated by multiplying an average fuel flow value (that the flight crew determined) by the duration of the flight. They arrived at a figure of about 79 tonnes. As this tallied well with the TOTALIZER fuel quantity figure, the flight crew concluded that the FUEL DISAGREE message was a spurious one and that there was no need to proceed with the FUEL LEAK checklist.

Several times on the return journey and as the aircraft approached Singapore, the flight crew was queried by the Air Traffic Control (ATC) if they needed any assistance. The flight crew replied that, other than the need to fly at the lower altitude of 17,000 feet, no assistance was needed as all other operations were normal.

Prior to landing, the flight crew jettisoned about 41,500 kg of fuel to bring the aircraft to below its maximum landing weight.

At 0649 hrs, the aircraft landed on the runway.

About 20 seconds after the thrust reversers on both engines were deployed, the occupants in the cabin heard two loud bangs, accompanied by two flashes, originating from the right engine area. At the same time, the flight crew heard a soft thud.

The Airport Rescue and Firefighting Service (ARFF) personnel who were monitoring the aircraft’s arrival informed the Control Tower on seeing the fire at the right engine. The Control Tower informed the flight crew of the fire and instructed the aircraft to stop at the intersection between the runway and rapid exit taxiway E7.

The flight crew did not receive any fire warning in the cockpit.

The ARFF which was on standby with four foam tenders and one water tender, entered the runway as soon as clearance to enter the runway was given by the Control Tower. The first foam tender arrived on scene after 57 seconds and started discharging foam at the right engine.

The fire was eventually brought under control (more on firefighting in paragraph 1.5). Disembarkation commenced at 0710 hrs (21 minutes after landing, ndr) via a mobile stairs positioned at the front left door of the aircraft.

All occupants, including the flight crew, vacated the aircraft by 0731 hrs.

CONCLUSION :

• The fuel leak in the occurrence flight was a result of a cracked tube within the MFOHE of the right engine. Fuel leaked into various areas of the engine through the core of the engine and the fan duct.
• When the thrust reverser was deployed during landing, the conditions at the area aft of the turkey feather seal of the core exhaust nozzle resulted in hot surface ignition of the fuel that had leaked from the MFOHE into the various areas of the right engine.
• As the fire developed, it propagated towards the forward section of the engine and entered the core of the engine through the fan booster inlet.
• The methods that were used to detect fuel leakage into the engine system by the operator and engine manufacturer were not able to detect the fuel leak that resulted from the cracked tube within the MFOHE when it occurred in that event flight.
• The engine manufacturer issued SB 79-0034 to address the issue of possible fuel leak in the MFOHE. The deadline for incorporating the SB was determined using the CAAM. The actions called for by the SB was not performed on the occurrence engine as the SB was issued after the engine’s last maintenance.
• In the course of the investigation, the engine and MFOHE manufacturers have identified that diffusion bonding can potentially cause any tube in the MFOHE to crack.
• The flight crew did not execute the steps in the FUEL DISAGREE checklist correctly.

The flight crew depended on the fire commander as their sole information source when deciding whether an evacuation was needed. Several other resources which could have aided them in making their decision were not utilised.

Singapore Airlines B777 at Changi Airport.jpg

Singapore Airlines Business Class 777

How to review an image[edit]

Any registered user can review the valued image candidates.Comments are welcome from everyone, but neither the nominator nor the original image author may vote (that does not exclude voting from users who have edited the image with a view to improving it).

Nominations should be evaluated using the criteria listed at Commons:Valued image criteria. Please read those and the page on scope carefully before reviewing. Reviewing here is a serious business, and a reviewer who just breezes by to say 'I like it!' is not adding anything of value. You need to spend the time to check the nomination against every one of the six VI criteria, and you also need to carry out searches to satisfy yourself on the 'most valuable' criterion.

Review procedure[edit]

• On the review page the image is presented in the review size. You are welcome to view the image in full resolution by following the image links, but bear in mind that it is the appearance of the image at review size which matters.
• Check the candidate carefully against each of the six VI criteria. The criteria are mandatory, and to succeed the candidate has to satisfy all six.
• Use the where used field, if provided, to study the current usage of the candidate in Wikimedia projects. If you find usage of interest do add relevant links to the nomination.
• Look for other images of the same kind of subject by following the links to relevant categories in the image page, and to any Commons galleries.
  • If you find another image which is already a VI within essentially the same scope, the candidate and the existing VI should be moved to Most Valued Review (MVR) to determine which one is the more valued.
  • If you find one or more other images which in your opinion are equally or more valued images within essentially the same scope, you should nominate these images as well and move all the candidates to an MVR.
• Once you have made up your mind, edit the review page and add your vote or comment to the review parameter as follows:

• If the nomination fails one of the six criteria, but in a way that can be fixed, you can optionally let the nominator know what needs to be done using the {{VIF}} template.

• Your comment goes immediately before the final closing braces '}}' on the page.

• Finally, change the status of the nomination if appropriate:
  • status=nominated When no votes or only neutral votes have been added to the review field (blue image border).
  • status=supported When there is at least one {{Support}} vote but no {{Oppose}} votes (light green image border).
  • status=opposed When there is at least one {{Oppose}} vote but no {{Support}} votes (red image border).
  • status=discussed When there is at least one {{Oppose}} vote and one {{Support}} vote (yellow image border).

Remember the criteria: 1. Most valuable 2. Suitable scope 3. Illustrates well 4. Fully described 5. Geocoded 6. Well categorized.

Changes in scope during the review period[edit]

The nominator is allowed to make changes in scope as the review proceeds, for example in response to reviewer votes or comments. Whenever a scope is changed the nominator should post a signed comment at the bottom of the review area using {{VIC-scope-change old scope new scope --~~~~}}, and should also leave a note on the talk page of all existing voters asking them to reconsider their vote. A support vote made before the change of scope is not counted unless it is reconfirmed afterwards; an oppose vote is counted unless it is changed or withdrawn.