Jump to content

F-2

Members
  • Posts

    1070
  • Joined

  • Last visited

Everything posted by F-2

  1. Captor M is based of the extremely well regarded Blue Vixen radar from the sea harrier which you can read about in this article if so inclined. https://www.secretprojects.co.uk/threads/ferranti-radars-blue-falcon-blue-hawk-blue-vixen.1224/post-10340
  2. How about this garish monstrosity
  3. Mod would be fair, just like the F-16I mod.
  4. 70 page lecture notes on N019 Radar translated into English by the secretprojects forum. Just in case someone wanted to create a detailed radar model. Т12 RLPK ENG.pdf
  5. Did I suggest that? If I did it wasn’t intended.They simply mentioned they would like to do a Naval Phantom at some point and I said I thought the F-4S seemed to be the most capable choice.
  6. The F-4S was well after the initial fielding with far more reliable components. There were six "bars" that I remember. I don't recall the starting bar, but if the bars were numbered as such: 1 2 3 4 5 6 I believe the vertical scan pattern went something like: 2,4,1,5,6,3 It wasn't quite what one would expect. I don't recall it changing the bar scan pattern - but remember, the last time I worked on those things was 27 years ago. As far as modes - they could select PULSE, PD (both ACM modes) A/G (which was the ground mapping feature, 120º PPI (Plan Position Indicator) mode) and I believe T/C or TERRAIN - this last very obscure feature was very difficult for aircrew to understand; it was supposed to indicate to them the likelyhood of collision with terrain features when proceeding at high speed, low altitudes (eg:bombing runs). The antenna scan pattern was that of a "+" - Full Up, Full Down, Center, Full Port, Full Starboard, Center (repeat) The scan displays on both scopes was also a "+". However, a number of crashes occurred while using this mode, and it's use was discouraged by modifying a card in the LRU-10 (Cockpit Display Unit, aft cockpit, port side, just under the canopy rail) to display a large "X" on the screen. As mentioned above, the pilot could select DOGFIGHT mode, which would override the RIO's controls, select short pulse, 10 mile range, and enable VTAS acquisition by sweeping out the range gate upon the pilot's pressing the lower button on his joystick. The RIO had his own joystick, mounted to the right of the scope and above it. The RIO's stick was about the size of a screwdriver handle, or straight sausage-shaped on a ball mount. It had an "action" button under the middle finger, and a thumbwheel on the top. The thumbwheel controlled the antenna's elevation. The elevation was indicated on the scope as a short horizontal blip on the right side of the screen. Pressing the button halfway down was called "half-action", this would cause the antenna to be slaved to the RIO's stick, and would initiate 60ms PRF switching to prevent target eclipsing. There was also the "taboo" mode, "EMERGENCY". This mode was to be used ONLY if you were in actual combat, and you had a transmitter failure. This mode overrode all of the thermal sensors, and a number of other protection circuits. Selecting this mode might enable the transmitter to work for a short period of time, but at the likely cost of destroying a number of radar components. When a RIO selected this mode, it tripped a red flag on the knob, which could only be re-set by removing the knob with a small Allen-type wrench. That was one of the very first things we would check after a flight - if that flag was out, the RIO got a trip up to the Skipper's office for an ass-chewing. There may be more modes that I've forgotten. The last couple of years I was on active duty, we got F-4S's with the AWG-10A's in them, then I transferred to VMFA-122 which had the older F-4J's with AWG-10's again. One can't remember everything from 27 years ago null PRF was approximately 40ms in PD mode; but remember there still was minute adjustments made to the PRF at the end of every scan, and it would switch every 60ms during half-action or acquisition. One interesting aspect of the PD mode was the ground clutter notch. This looked rather like an inverted arch. The faster the aircraft was travelling, the taller and narrower the arch was. It was, literally, a "black hole" - the radar would not "see" anything in that notch. It would take digital signal processing to make use of that ground clutter return, which wasn't until later. Remember, the electronics in the AWG-10 were quite crude by today's standards - their idea of an integrated circut back then was a collection of discrete components surrounded by a black cube of epoxy. This is also what made it so difficult to repair, and gave it a low MTBF. The MTBF on the original AWG-10 radars we had was quite dismal; if an aircraft was still "up and up" (airframes/radar) for three "hops" (sorties) it was golden. Remember, these aircraft were doggone old by the time I got to operational squadrons back in 1975; they were all Vietnam Veterans, and had seen MANY launches/recoveries from aircraft carriers, and were very high-time airframes. A single F-4J Phantom had 15 miles of wire in it. That's a lot of wiring to maintain. Much of it involved the radar. And the radar had quite a few electro-mechanical relays. One of our most frustrating "gripes" would be, "Radar breaks lock under G's" to which we could only reply "G-force simulator on back order." They wouldn't let technicians fly in the backseat - so we couldn't begin to troubleshoot it. The BIT box (LRU-8) was a troublesome piece of equipment (BIT=Built-In Test) - it was driven by a film strip with written instructions and frame numbers to tell you where it was in the test, and a grid of (logical) 1's or 0's (either black or see-through) that drove a series of either phototransistors or photoresistors, which controlled a "relay tree" above the antenna that would select various circuits to test. This thing was a nightmare in itself. The AWG-10A BIT box was infinitely better; it was all digital, and markedly faster. When my 1st squadron got the very first F-4S's with the AWG-10A radars in them, we found them to be VERY reliable in comparison - we were getting 10, 20, 30 or more hops between repairs. However, the first time we went to swap out a computer (LRU15 or LRU16, can't remember which) in the turtleback (behind the RIO) we discovered that the computer harness had been made too short! We got the cables off OK, but they just wouldn't go back on the new computer. They'd made an error in measuring the "jig" used to build the cables. The F-4S's had other teething problems. They changed from the old flammable hydraulic fluid to a new, non-flammable hydraulic fluid; however the old O-ring seals were not compatible with this new fluid. Well, they supposedly replaced all of the O-rings when the airframes were rebuilt, but they missed a few in the turtleback area, causing eventual massive hydraulic leaks and our squadron to nearly lose an aircraft after losing all hydraulic pressure during approach.[/quote] I left the Corps before those missiles were available. The Sparrow missiles I worked with connected to the missile umbilical using a 32-pin shear "wafer". When the missile was ejected from the rack (by firing what amounts to a blank shotgun-shell type device) the wafer would actually shear in half; one side would remain attached to the missle, the other half would stay with the harness. I have a couple of these "wafers" left from my tour in the Corps; I was using them to build Sparrow missile simulators so the aircrew could practice locking on the radar and firing when the missile was inside the envelope. Don't have any photos - yet. They're rather crude, we didn't have any circuit card material available - just soldered together a dozen resistors, capacitors and diodes along with a fuse holder, then potted the whole thing. You're welcome - hope this is enough for the moment. It's after midnight here, it's been an event-filled day, and I have more to accomplish before hitting the rack. From the secret projects forum on APG-59
  7. Well in terms of radar the F-4S is vastly more capable the the E.
  8. I think all F-16 block 40,42,50,52 have the software to fire sparrow, and in theory it can be applied to block 25,30,32 aircraft (I’m not sure it ever has) However Sparrow requires a special hard point that most operators simply never ordered by most. Egypt, Iraq, Singapore, and Bahrain I believe are the only ones that did. Bahrain *might* have carried AIM-7F on their block 40 vipers in the Gulf war. There are pictures of the timeframe with the missile but no exact date. The jets where factory fresh and the missiles where ordered in the late 80s but nothing definitive.
  9. Peter Bowers built a number of replica WWI aircraft in the 60s and 70s. He’s no longer living but perhaps someone could contact his family to see if they saved any of his documentation?
  10. We are getting a mechanical scan version. They didn’t totally rule out AESA but it’s extraordinarily unlikely. The Typhoon never had a PESA, you might be thinking of the Rafale.
  11. F-4S might be the best plausible phantom for air quake barring the AMRAAM phantoms. Which is in its own right a good selling point.
  12. No prob, I’m impressed that even manuals are available. It would be nice to know if I should hope the Naval Phantom is a S or a M/K. I’m interested if either come close to this bad boy.
  13. I didn’t even know we had charts for the British Phantoms. I’m curious how capable they where. if we want to know what was the very best turning Phantom , this is something of a cop out but the IsraelI PW1120 powered phantom had a degree and a half sustained turn rate advantage over an equivalent E.
  14. I thought this was surprisingly detailed for what it is. Very impressive even compared to the post CCIP block 50
  15. Maybe the real Phantom was the friends we made along the way!
  16. I’ve been hoping! That and Chinese new years is in a month
  17. Behold the superman
  18. In one hand I want know what’s coming (if anything) on the other hand I love how cold it is. “You want to know the next plane? You’ll see on release day.” If I had the talent to make a module I’d kill to be that cool .
  19. So I tried to see if the government had anything on the Yak-141 and by extension the Yak-38 from the JSF deal. But it seems they only have sim technical briefings. It seems you would have to get in contact with Lockheed.
  20. We have some very detailed info on the N019. If it’s ever uncancelled we could get a very realistic radar model.
  21. ASM-2 as well. F-4EJ was quite capable in the anti shipping role.
  22. For all we know (and I’m saying this as a possibility not a statement of fact, please don’t misconstrue) it could very well be in the 2023 and beyond trailer.
  23. Years ago there was supposed to be an Su-35 (Su-27m) flight simulator made with assistance of Sukohi and test pilots who flew the real thing but it never was released. Supposedly their was supposed to be a beta. http://web.archive.org/web/19991002084308/www.aha.ru/~gland/ This gaming magazine seems to have had a copy. https://m.igromania.ru/article/19131/Kladbische_russkih_igr._Otechestvennye_proekty_konca_devyanostyh_tak_i_ne_uvidevshie_svet.html id be interested in at least examining it. also of note the sim seems to have been used to make a desktop trainer Su-30 for the Indian Air Force. The demo version without the cockpit avionics is still available. I thought that could be used as a reference to make an AI Su-30sm.
  24. https://books.google.com/books?id=3JEpAQAAIAAJ&q=apg-63(v)2+society+of+experimental+test+pilots&dq=apg-63(v)2+society+of+experimental+test+pilots&hl=en&newbks=1&newbks_redir=0&source=gb_mobile_search&sa=X&ved=2ahUKEwjb4a2mq4T8AhXhMlkFHdNrCRYQ6AF6BAgDEAM#apg-63(v)2 aesa APG-63(v)2 flight test data?
×
×
  • Create New...