Recover from hot start
-
I allow RPM to increase to above 750 and throttle go CUTOFF before 800 since Dash 1 says “If you see FTIT rising at an alarming rate or go above 750°C you are encountering a hot start”
Not sure if JFS is off but I do not turn it off and during cooldown, the JFS sound still on, light still on, switch still on Start 2 position. -
That with the canopy is just plain WRONG. Here’s the proof. There is no problem closing canopy with just started JFS.
Look at video 3:34 onwards … Actually it is Thunderbird’s F16 .
SO… BMS is WRONG in this matter… just dare to say its fake
-
That with the canopy is just plain WRONG. Here’s the proof. There is no problem closing canopy with just started JFS.
Look at video 3:34 onwards … Actually it is Thunderbird’s F16 .
SO… BMS is WRONG in this matter… just dare to say its fake
no it’s not wrong,
it’s not systematic, there is a PROBABILITY that JFS shuts down in BMS when closing canopy, as in real
refer to proper engineering documentation
-
Ok, I’ll take that, but it REALLY seems like a far remote PROBABILITY ,… like ‘Pilot’ is not worried about it at all (of course, generator is behind corner) , but, He is not interrupting his 'automation powerup script not a single moment.
So , that PROBABILITY should be set to 1-5% , not more. … - I have no problem with the RTFM and with following procedures but it would be nice that procedure would be close to the truth as much as possible, since we enjoy quite a real sim… so be it. :thumb:
-
I allow RPM to increase to above 750 and throttle go CUTOFF before 800 since Dash 1 says “If you see FTIT rising at an alarming rate or go above 750°C you are encountering a hot start”
Not sure if JFS is off but I do not turn it off and during cooldown, the JFS sound still on, light still on, switch still on Start 2 position.RPM is from 0-100%. There is no “750 RPM.”
You cannot let FTIT go above about 750°C during a hot start of the engine will break and never run again. The tip is how to identify a hot start which is an alarming rise or any time being above some temperature (which won’t be reached at any pace during a normal start). Notice the word “or.”
An alarming rise that also reaches ~700-750°C (and, not or) is unrecoverable. It is identifiable as a hot start but a second start will not be possible. It’s not the JFS’s fault. JFS continues to run but won’t turn the engine. You can shut down completely, recharge the accumulators and try again and you won’t get any RPM. I always get the “ENG FIRE” warning associated with an unrecoverable engine failure.
-
Sorry, I mean FTIT above 750, not RPM.
If you see FTIT rising at an alarming rate or go above 750°C you are encountering a hot start
As not a pilot, I do not know what is or not alarming rate. As not a pilot, I know what is go above 750C, so that I follow. The word “or” means I can follow either, no?
FTIT should not go above 800°C. If you see FTIT rising at an alarming rate or go above 750°C you are encountering a hot start; immediately pull the throttle back to CUTOFF and let the FTIT decrease to 200°C while the JFS is running, before attempting another engine start.
I do not get FTIT above 800C, put throttle go CUTOFF between 750-800C. I copy above from Dash 1 page 166 and from reading, it sounds like it can possible to restart engine and not unrecoverable.
-
RPM is from 0-100%. There is no “750 RPM.”
You cannot let FTIT go above about 750°C during a hot start of the engine will break and never run again. The tip is how to identify a hot start which is an alarming rise or any time being above some temperature (which won’t be reached at any pace during a normal start). Notice the word “or.”
An alarming rise that also reaches ~700-750°C (and, not or) is unrecoverable. It is identifiable as a hot start but a second start will not be possible. It’s not the JFS’s fault. JFS continues to run but won’t turn the engine. You can shut down completely, recharge the accumulators and try again and you won’t get any RPM. I always get the “ENG FIRE” warning associated with an unrecoverable engine failure.
the temperature of fire depends on the engines !!!
so some of them can afford much more than 750 , some others can’t…
PW 200 & PW 220 :
ground fire 720 deg
PW 229
ground fire 840 deg
GE 100
ground fire 980 deg (it should be 880 here, this is a bug)
GE129
ground fire 880
that could be the OP problem
what block do you use ?
-
If this is the first training TE (white and red fuselage, two seat Viper), then it’s a Block B, with either a 200 or 220 engine.
Dash-1 is written for Block 50/52, which means some specific details are are not correct for older blocks. In particular, there’s less leeway for dealing with hot starts on older engines.
-
Best would be to have markings on FTIT gauges for each engines models …
ex:
-
Best would be to have markings on FTIT gauges for each engines models …
ex:
Or in russian way. Rotate all meters so that when they point north all is ok.
-
@M79:
Or in russian way. Rotate all meters so that when they point north all is ok.
Call/ask Lockheed Martin for that.
-
What are the chances of getting a hot start in the sim if you follow start procedure properly?
-
Thank you to Mav-jp and Dragon1-1 for patience! I do not know what F-16 version but I use TE 01 and it look like engine fire always after 700C FTIT. Is no way to recover from engine fire, no? Just restart mission? Or can still restart engine but longer (JFS refuel, etc.)?
I confirm by try benchmark test TE and engine fire only after 800C FTIT and can follow Dash 1 instruction of restart engine after hotstart with 750-800C FTIT.
-
This post is deleted! -
What are the chances of getting a hot start in the sim if you follow start procedure properly?
2%
-
-
If your throttle has a detent, like the warthog, there is the ability to assign keystrokes/ dx buttons to points before and after the detent. Maybe you have the JFS toggle or JFS off accidentally assigned to one of those points. That would explain jfs being turned off while moving throttle to cut off position and JFS not keeping rpm at 20% even though you don’t flip the switch.
-
Call/ask Lockheed Martin for that.
I called. That on their next update that’s ready in 4 weeks.
Serious, that’s quite good way to check that things are ok with fast glance.
-
@M79:
that’s quite good way to check that things are ok with fast glance.
Sure. But we won’t do that in the Sim of course.
-
Understandable. Sim should do like real one.