LiveATC Discussion Forums
Air Traffic Monitoring => Aviation Audio Clips => Topic started by: PRFlyer on November 20, 2011, 04:21:00 PM
-
Philippine Airlines PR103, LAX to MNL with a Tech Stop in GUM, aborted its takeoff on November 17 after a misconfigured take off setting warning.
After exiting runway 25R, it was on Taxiway Bravo when the heat fuse of several of the MLG tires activated and deflated them. As of Friday, it was being repaired on the Taxiway.
-
It has been sitting in a cargo un load zone. Wondered why it had been there since Friday.
-
Here is where it has been sitting for the last few days. Cant see now cause it is dark but maybe in the morning it will be there. http://www.cargolaw.com/lax_webcam.html
-
http://www.avherald.com/h?article=44659d80&opt=0
-
Philippine Airlines PR103, LAX to MNL with a Tech Stop in GUM, aborted its takeoff on November 17 after a misconfigured take off setting warning.
After exiting runway 25R, it was on Taxiway Bravo when the heat fuse of several of the MLG tires activated and deflated them. As of Friday, it was being repaired on the Taxiway.
Could you kindly explain what do you mean of misconfigured take off? i presumed the warning was in the cockpit? what is the proper procedure for the captain of the plane to inform the passenger of what went wrong? is there any update regarding FAA investigation report regarding this incident? thank you.
-
Philippine Airlines PR103, LAX to MNL with a Tech Stop in GUM, aborted its takeoff on November 17 after a misconfigured take off setting warning.
After exiting runway 25R, it was on Taxiway Bravo when the heat fuse of several of the MLG tires activated and deflated them. As of Friday, it was being repaired on the Taxiway.
Could you kindly explain what do you mean of misconfigured take off? i presumed the warning was in the cockpit?
That means the aircraft was not properly configured for takeoff, meaning, for example, the flaps and slats were not in the correct position, or something along those lines.
-
is there any update regarding FAA investigation report regarding this incident?
The NTSB publishes investigation reports here. If you know the date of an accident anyone can look up whatever is of interest.
An incident does not necessarily qualify as an accident (per NTSB 830), so there may be no further investigation.
http://www.ntsb.gov/aviationquery/month.aspx
-
This would not qualify as an accident per NTSB 830 and therefore they probably were not even notified. The FAA may investigate to see if there was an FAR violation which there probably wasn't.