A320 Hot Weather Ops Question
Thread Starter
Join Date: Mar 2016
Location: Seattle
Posts: 3
Likes: 0
Received 0 Likes
on
0 Posts
A320 Hot Weather Ops Question
I've researched this and haven't found an answer yet.
For example, say your company policy is to leave the flaps at 1+F on taxi in to avoid an AIR L (R) WING LEAK warning when temperatures are >30 C or more.
Your the new crew that picks up the plane that just came in. You do your preflight checks and come to the Take Off CONFIG check. I'm thinking the test won't work because the flaps/slats were left in the take off position (1+F).
So, my question is:
What are other operators doing at this point?
Are they retracting the flaps/slats to up and then doing the Take Off CONFIG test?
Are other operators lowering the flaps/slats to 1+F after completion of the Take Off CONFIG test?
Thank you in advance!
For example, say your company policy is to leave the flaps at 1+F on taxi in to avoid an AIR L (R) WING LEAK warning when temperatures are >30 C or more.
Your the new crew that picks up the plane that just came in. You do your preflight checks and come to the Take Off CONFIG check. I'm thinking the test won't work because the flaps/slats were left in the take off position (1+F).
So, my question is:
What are other operators doing at this point?
Are they retracting the flaps/slats to up and then doing the Take Off CONFIG test?
Are other operators lowering the flaps/slats to 1+F after completion of the Take Off CONFIG test?
Thank you in advance!
The test does work -the takeoff config pb does just what it's meant to - amongst other things testing that the flaps are not at 0. That's satisfied by the residual 1+F. There is no requirement for the takeoff config test to be done at Flap 0 (in fact you'll get a very loud warning!) which seems to be what you're implying?
And that's why the cockpit setup procedure has for Flaps to check that the handle matches the flap indication on the ECAM. thus it can be at Flap 1.
And that's why the cockpit setup procedure has for Flaps to check that the handle matches the flap indication on the ECAM. thus it can be at Flap 1.
Last edited by compressor stall; 4th May 2016 at 10:26.
We don't use the take-off config test when preparing the aircraft on the ramp before pushback.
We use it just before we line up on the runway. It is to simulate the application of take-off engine power, and if any monitored system is not set correctly, a master warning will be triggered. This test allows us to remedy the mis-selection before we actually apply take-off power.
Flap setting is one parameter which is tested in this way. If the actual flap setting is not the same as that which we have programmed in the take-off performance page of the FMGS the config warning will be triggered.
We use it just before we line up on the runway. It is to simulate the application of take-off engine power, and if any monitored system is not set correctly, a master warning will be triggered. This test allows us to remedy the mis-selection before we actually apply take-off power.
Flap setting is one parameter which is tested in this way. If the actual flap setting is not the same as that which we have programmed in the take-off performance page of the FMGS the config warning will be triggered.
Join Date: Apr 1999
Location: UK
Posts: 1,691
Likes: 0
Received 0 Likes
on
0 Posts
We tend to run a mix of Airbus/company/we-did-it that-way-on-Boeing procedures on our Airbus fleet but we only press the TO Config test as the last item on the Before T/O checklist. Who's pressing it before then, and why?
Join Date: Aug 2015
Location: France
Posts: 167
Likes: 0
Received 0 Likes
on
0 Posts
If the actual flap setting is not the same as that which we have programmed in the take-off performance page of the FMGS the config warning will be triggered.
Join Date: Oct 2015
Location: 43N
Posts: 264
Likes: 0
Received 0 Likes
on
0 Posts
If the actual flap setting is not the same as that which we have programmed in the take-off performance page of the FMGS the config warning will be triggered.
These guys got caught out (and the skipper thought the same as you).
https://www.atsb.gov.au/media/519998...29%20Final.pdf
Join Date: Mar 2006
Location: USA
Posts: 2,524
Likes: 0
Received 0 Likes
on
0 Posts
Uplinker - as others have said the T/O CONFIG just checks that there is a plausible flap setting for takeoff (CONF1, 2 or 3). It does NOT xcheck the FMGC.
Join Date: Aug 2013
Location: Middle Europe
Posts: 80
Likes: 0
Received 0 Likes
on
0 Posts
depending on your FMGS software standard you will receive an ECAM caution "F/CTL FLAP/MCDU DISAGREE" after pressing TO CONFIG pb/applying TO power if MCDU and actual flap setting don't match. this update also incorporates a function which compares your typed in TO speeds to VMC/Vs1g from an internal database. in case your inputs were too low for your entered ZFW, blockfuel, TO config then FMGS will notify you via an amber scratchpad message "TO SPEED TOO LOW"
i must admit those functions came with a fairly recent update though.
i must admit those functions came with a fairly recent update though.
Join Date: Mar 2006
Location: USA
Posts: 2,524
Likes: 0
Received 0 Likes
on
0 Posts
i must admit those functions came with a fairly recent update though.
Join Date: Mar 2012
Location: Having a margarita on the beach
Posts: 2,423
Likes: 0
Received 0 Likes
on
0 Posts
Hi Check Airman,
pick up an msn and check in DSC-22 MCDU message list (don't have the FCOM handy so can't give you the proper reference) if the the "TO SPEED TOO LOW" message is there. Check in PRO-ABN F/CTL if the caution FLAP/MCDU DISAGREE is there as well.
Cheers.
pick up an msn and check in DSC-22 MCDU message list (don't have the FCOM handy so can't give you the proper reference) if the the "TO SPEED TOO LOW" message is there. Check in PRO-ABN F/CTL if the caution FLAP/MCDU DISAGREE is there as well.
Cheers.
Maybe not in your operator's FWC software. Airbus are happy to change the FWC warnings on operator request. And of course different configurations will require this.
Join Date: Nov 2006
Location: Tropics
Posts: 359
Likes: 0
Received 0 Likes
on
0 Posts
We have the F/CTL PITCH TRIM/MCDU/CG DISAGREE warning, but not the FLAP/MCDU disagree warning.
It's a recent update like the others have mentioned. But I would have thought the FLAP/MCDU discrepancy would be included in the update.
It's a recent update like the others have mentioned. But I would have thought the FLAP/MCDU discrepancy would be included in the update.
Join Date: Aug 2013
Location: Middle Europe
Posts: 80
Likes: 0
Received 0 Likes
on
0 Posts
to my knowledge it's FMGS update S7A/T5A (thales) but i have no other idea than asking your engineering department which software is in your magic box.
documentation-wise in the FCOM i can't find a reference either. this update was announced to be successively introduced to our fleet in the near future. maybe the fact that this update is not fully implemented yet is the reason why the FCOM is still lacking information about this new (hidden
) features.
documentation-wise in the FCOM i can't find a reference either. this update was announced to be successively introduced to our fleet in the near future. maybe the fact that this update is not fully implemented yet is the reason why the FCOM is still lacking information about this new (hidden
) features.
Last edited by sierra_mike; 12th May 2016 at 10:41.
Join Date: Oct 2010
Location: 5° above the Equator, 75° left of Greenwich
Posts: 411
Likes: 0
Received 0 Likes
on
0 Posts
We operate in tropical weather so we do a lot of that flaps 1+F after landing. It makes no difference as far as the function of the TO config pb goes. We press it on taxi pattern flow we use before running the before takeoff check. Our aircraft also test for "flaps on feasible takeoff config", it doesn't give a monkey whether that's 1+F, 2 or 3, something I feel it could be quite handy for us as we usually use 1+F for most takeoffs and therefore one can easily select 1+F from memory instead of 3...
