BMS 4.34 Documents correction report
-
-
edit: nvm, my brain was using the PFD on what I fly approaches on, which has a bar on the bottom and the side for loc and gs, respectively, instead of what Falcon uses_….
…which means the manual is CORRECT as is, I was wrong lol_
Firstly, thank you for the amazing piece of work produced…the charts, the manuals, …everything is amazing
Found an simple error where the ILS vertical and horizontal aspects where mixed up in the explanation, looks to be a simple swap.
BMS-Training manual, Mission 4: Night ILS Landing, pg 47:
"…The first emitter is vertical and called the localizer. It guides aircraft
to the runway centreline. The localizer is represented in the cockpit by a vertical bar in the HUD, ADI and HSI.The second emitter is horizontal and guides the aircraft on the optimal glide path to the runway (3° in BMS). It
is called the glide slope and is represented in the cockpit by a horizontal bar in the HUD and the ADI."Might leave a few new guys scratching their heads…lol
-
Why do you this is oncorrect. Vertical for line-up, horizontal for altitude. Makes perfect sense to me. What am I missing here?
-
:doh: …… :tape2:
-
-
BMS Training Manual V 1.2 Mission 11: Laser guided bombs
Page: 99
…and ground-stabilise the TP with TMS up.
Page 102:
As we approach the target the TGP cursors can be moved…
and
TGP cursor position can still be moved while the bomb is guiding.
I have been struggling with this. After ground-stabilizing with TMS up, I couldn’t properly slew the TGP cursor to the base of the crane. It just kept jumping back to what seemed to be the initial tracking point. With TMS right (area track) it did work and I could move the cursor to the base of the crane, as suggested.
The 34-1 manual explains on page 150 that after a slew in point track, the TGP will try to establish point track again so that explains what i first thought to be erratic behaviour.
The manual is not wrong perse, but my confusion about the slew-behaviour could have been prevented (even considering I’ve read the 34-1 beforehand, but that sort of faded when trying to follow the training manual to the letter).
Suggestion for this missions text:
- use Area Track to ground stabilise to immediately show the slew behaviour hinted on page 102 (so advise TMS-right instead of TMS-up) without the need for deeper knowledge.
- or explain the difference between point track and area track and try to teach the pilot when to use what option (but this would require a bit of copy/paste from the 34-1, making it the lesser option)
Whatever might be done with my suggestion: it has been an educational process nonetheless
-
BMS Technical Manual Pg 3-24
RSAF should be " REPUBLIC of Singapore Air Force".
Singapore does not have a king or royal family…
Edit RD [Fixed] -
BMS Training Manual V 1.2
mission 13, page 121
“Intel reports suggest that both AAA are located very close to the village on the eastern side. It is valuable information, as it should decrease your search time.”
from the briefing page i think they are on the western side of the village, not the east side, can you confirm that?EDIT:
it is a my fault, i have to hit the ZSU-23s that are at the east side of the village, not the other vehicles on the west sideOk the docs is pretty right
sorry -
In the BMS 4.34 Training manual for TE 13 AGM-65 MAVERICKS on p. 129
The HUD is made SOI by default, indicated by the asterisk in the top left corner and the TD box is placed on the FPM. You can move the TD box in the HUD with the cursors. Place it on the outer left span of the bridge. TMS up to ground-stabilise the TD box and SOI automatically transfers to the WPN page.
But TMS up doesn’t automatically transfer SOI to WPN page. If you follow along the TE TGP is still active and as of TO-BMS1F-16CM-34-1-1 p. 188
Designating the target ground stabilises the TD box on or near the target and automatically moves the SOI to the TGP or WPN MFD page (TGP has priority if active).
So in my opinion either include the additional DMS down required in the Training manual.
Regard oakdesign
-
Short note of thanks to everyone taking their time to work through the manuals and highlighting potential issues !
-
-
In the BMS-Comms-Nav-book at the top of page 134 there is a rule of thumb for descent rate.
However if I didn’t mess up somewhere, this rule of thumb would only apply for an aircraft travelling at 1nm per minute, i.e. 60kts. Maybe add a factor 5 in there to get a more sensible 300kts estimate.Thanks for the amazing documentation.
Nicolas
Edit RD [Fixed]
-
Correct. To loose 15000ft in 30Nm flying at 300KCAS you need about 3000ft/min.
-
Hello,
In the manual BMS TECHNICAL MANUAL
Chapter: 9.6 Managing two radios
Last line: More information can be found in chapter 12.10It should read: 13.9 New 4.34 Options
Thanks again for all the work provided!
Edit RD [Fixed] -
probably very small typo:
BMS-Comms-Nav-book.pdf - 5.2 Starting engine - page 125
“When you enter .125 decimals in the F-16 radios only .22 is displayed.”
I think it should say “… only .12 is displayed.”
Thanx Red Dog for your docu
SunnnyEdit RD [Fixed]
-
https://www.benchmarksims.org/forum/showthread.php?37596-Pre-Flight-newb&p=522514&viewfull=1#post522514
dash-1 canopy - location of the hotspot is wrong in manualEdit RD [Fixed]
-
@Red:
https://www.benchmarksims.org/forum/showthread.php?37596-Pre-Flight-newb&p=522514&viewfull=1#post522514
dash-1 canopy - location of the hotspot is wrong in manualDon’t bother to fix that one, it will change in the future version (not future patch/update).
-
page 123, preset 9 is not ALT ground, it is preset 12.
Edit RD [Fixed] -
With the C&I switch in C&I all IFF settings are changed through the UFC?
is this a typo? i m not sure.
Edit RD (dumplicate) [Fixed]
-
this is not an error but a suggestion.
in BMS-training.pdf, page 146 147, u put a lot words on STPT selection. but that is a very easy concept i can understand in just 3 sentences. u don’t need 2 pages to explain it.
but in page 151, only one sentence “Should you need to pickle before reaching the top of the LAR, the bomb will fly straight to the target and ignore the impact azimuth” talk about impact azimuth limitation.
and base on my tests, azimuth only work with 60 deg offset.
e.g. i fly heading 090, the azimuth must be set in 30-150, otherwise it dosn’t work. but the manual (and other pdf) put no word on this.