pete_auau Posted August 20, 2019 Posted August 20, 2019 Hi all need some help, I know how to do the case1 landing etc fly overhead the carrier 2000 than descend down to 800 feet fly to the right of carrier. Break to the left around 1 km past the carrier down to 600 feet 1.2 abeam from the carrier than descend down to 400 feet to land on carrier, I have no issues in doing this the issue is that iam not getting the landing clearance from atc to land I call atc to land around say in this case around 12 km from carrier it tells me to fly 018 for 9 qfe29.33 rwy33( I assume this means fly 018 for 9000 feet) for pattern altitude I fly to the carrier at 018 at angels9 and at 5kms from carrier to begin a circle the carrier at 5km distance after awhile I get a response from the carrier 10 tower roger brc is 24 signed is Charlie( in which I set the course to 240 ) this is where I get confused on the procedure to get landing clearance to land I than proceed to descend down to 800 feet behind the carrier around 6km to fly abean to check if if deck is clear etc and than proceed on case landing but I dont get any atc to land request? Obviously iam doing some thing wrong here. I have seen wags and jabbers tutorial on landing
Bones1775 Posted August 20, 2019 Posted August 20, 2019 first of the 9 is distance not altitude. for another this" fly 018 for 9 qfe29.33 rwy33( I assume this means fly 018 for 9000 feet) for pattern altitude" has no rellavence in the case 1 recovery. since carrier comms are still WIP there is still overlap from the original ATC comms. i assume once it is complete it will go away. check out lex's videos here https://www.youtube.com/channel/UCPqnAPcQSxyCqJ0CZu9qMmgfor an expznation of opps around the boat. "10 tower roger brc is 24 signed is Charlie( in which I set the course to 240 ) " this is telling you the CVs course is 24 degrees not to fly 240 degrees. this may help as well. https://wiki.hoggitworld.com/view/Carrier_Air_Operations
Harker Posted August 20, 2019 Posted August 20, 2019 BRC 24 means that the carrier's magnetic heading is 24, not 240. It doesn't work like runways (where 24 would mean 240 true heading). At least that's how the above works in DCS right now. Also, I noticed that the BRC they give you is 2 degrees less than the correct one, so I'd use 26 in that example, instead of 24. The "018 for 9 QFE 29.33 RWY 33" is a remnant of the ATC used in airfields in DCS and not applicable for carrier approaches. The only useful part is the QFE, which I think you get during mom's response anyway. I've found that a consistent way to get a proper response from the carrier is to declare "Inbound" twice. First time, you'll get the useless generic ATC response and the second time you'll actually get the "new comms" response. That and another response when you're in the overhead pattern, once you fly over the carrier. I've also had LSO comms a couple of times, including a grade, but I haven't found a way to get this to work consistently. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Gierasimov Posted August 20, 2019 Posted August 20, 2019 Inconsistency must be related to the fact that carrier comms we get now in beta was not meant to be released at all and slipped with internal testing, at least that is what was explained. I bet, that there will be training videos once the new comms system is released with the Supercarrier module. Intel Ultra 9 285K :: ROG STRIX Z890-A GAMING WIFI :: Kingston Fury 64GB :: MSI RTX 4080 Gaming X Trio :: VKB Gunfighter MK.III MCG Ultimate :: VPC MongoosT-50 CM3 :: non-VR :: single player :: open beta
ac5 Posted August 20, 2019 Posted August 20, 2019 Inconsistency must be related to the fact that carrier comms we get now in beta was not meant to be released at all and slipped with internal testing, at least that is what was explained. I bet, that there will be training videos once the new comms system is released with the Supercarrier module. I understand, but then why are this inconsistencies present in the release version? They should be present only in the beta, otherwise what's the point of a release and a beta DCS world versions? Mainboard: ASUS Maximus X Hero Intel Z 370 CPU: Intel Core i7-8086K @ 4.0 GHz Memory: 32GB Corsair Dominator Platinum DDR4-3000 Graphics Card: ASUS NVIDIA GeForce RTX 3080 10GB Monitor ASUS PA 329 32" @ 4K 1 SSD Samsung 860 PRO 256 GB 1 SSD Samsung 860 PRO 4 TB Windows 10 - 64 V. 2004 CH Pro combatstick, throttle and pedals
victorlima01 Posted August 20, 2019 Posted August 20, 2019 QFE should never be referenced in the carrier environment, only QNH. But since the carrier is operating at MSL QFE will always be the same as QNH. However, it is incorrect to reference QFE. For now I would not worry about comms during case I recoveries. You can grab the carrier's BRC from the F10 view, and plan to join the stack accordingly. Getting authorization to land for now is only important in Case III recoveries since you need the lighting to work.
Harker Posted August 20, 2019 Posted August 20, 2019 QFE should never be referenced in the carrier environment, only QNH. But since the carrier is operating at MSL QFE will always be the same as QNH. However, it is incorrect to reference QFE. For now I would not worry about comms during case I recoveries. You can grab the carrier's BRC from the F10 view, and plan to join the stack accordingly. Getting authorization to land for now is only important in Case III recoveries since you need the lighting to work. I agree about the QFE vs QNH for a carrier approach. I think DCS has it wrong, since the ATC assumes that the carrier deck is at MSL, while it actually is at a 70ft elevation. The comms say QFE, but they actually give QNH. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Recommended Posts