The system was operated by the 32nd Regiment Royal Artillery. Phoenix attrition was high during the Iraq campaign, though British Army officials say it gave excellent service for artillery spotting, stating that some of the losses were due to deliberate sacrifices, in which the UAV was kept on station beyond the time it could be recovered rather than let targets get away. The Phoenix eventually entered service in 1999, and saw limited operational use as part of the British contribution to Kosovo Force (KFOR) and in Iraq as part of Operation Iraqi Freedom. The first flight was in 1986, with an expectation that it would enter service in 1989, but the project suffered from numerous delays. The name Phoenix was taken from Project Phoenix, a late 1970s study into surveillance and target acquisition needs after cancellation of the unsuccessful development of Westland MRUASTAS to replace AN/USD501 Midge. A second UAV can be launched within a further eight minutes and up to two UAVs can be controlled from the same ground station. The UAV could be launched within an hour of reaching its launch site. The principal method of communication from the GCS to artillery on the ground was via the Battlefield Artillery Target Engagement System (BATES). Phoenix sensors provided imagery direct to the GCS where it was analysed and reported to artillery headquarters, to command level, or to a Phoenix troop command post. The zero-length take-off and landing was an essential requirement for operating in NATO's Central Region and deployment in a forward divisional area. The Phoenix was recovered by parachute, landing on its back, with a crushable "hump" on the back taking up the impact. The launch rail having been originally developed for the US Army Aquilla UAV that failed to enter service. Phoenix was 'zero-length' launch being projected into the air from a launch-rail mounted on the back of a truck. Phoenix was mostly made of Kevlar and other plastics. This tends to obstruct a sensor turret, and so the sensor payload, built around an infrared imager, was carried in a pod slung well under the fuselage. The Phoenix was a fairly typical combat surveillance UAV, powered by a 20 kW (26 hp) piston engine, but is distinctive in that it is a "tractor" aircraft, with the propeller in the front. It was the third generation of UAV in British Army service with the Royal Artillery after SD/1 and Canadair Midge. It had a twin-boom UAV with a surveillance pod, from which the imagery was data linked to a ground control station (GCS) that also controlled the aircraft in flight. The BAE Systems Phoenix (originally GEC-Marconi Phoenix) was an all-weather, day or night, real-time surveillance Unmanned Air Vehicle. The motors are paired with 12A ESC and 3-leaf propellers.British Army Phoenix Phoenix displayed at the former REME Museum of Technology site at Arborfield 2s 450-600mah or 3s 450mah-550mah LiPo batteries are suggested Īt the end of each arm is located a powerful GR1106 4500kv brushless motor.RunCam Micro Swift 600TVL FPV camera w/ 2.1mm lens.Powerful GEPRC GEP-GR1106 4500kv brushless motors.GEPRC STABLE F4 Tower (VTX, ESC & Omnibus F4 flight controller with BetaFlight OSD). Carbon fiber & aluminium camera protection frame.125mm sized carbon fiber frame (3mm bottom plate).The real-time image transmission is provided by a 5.8G-48CH VTX with broadcast power of up to 200mW. In front of the GEPRC Phoenix is located a RunCam Micro Swift camera. Through the BetaFlight Goggle Apps, you can configure multiple flight modes. Like most of the recent FPV racing quadcopters, the GEPRC GEP-PX2.5 is also based on the versatile Omnibus F4 flight controller. While it can be powered by 2s and 3s batteries, the max speed can be achieved only by using 3s LIPOs. Surely, with flight speed of up to 120Km/h, this new GEPRC GEP-PX2.5 Phoenix FPV drone is recommended only for experienced pilots.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |