Skip to content
View in the app

A better way to browse. Learn more.

HarpGamer

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Pioneer UAV in H4.1

Featured Replies

While it does not appear in Annex B, here is what I have gleened from the manufacturer and fas.org. They give roughly the same info:

 

Size/Signature: VSmall (my idea)

Sensor: CCD (Day only) or FLIR (Day/Night) (would need to assign a generation)

Ceiling: 15,000 feet

Speed: 65kts Cruise, 110kts "dash"

Range:100km

Fuel: 11 USG

 

Would you like to add anything to that?

  • Author

I got word back from someone close to the Admiratly that the pioneer numbers look good and should work, so I will be employing these in the very near future.

 

Any comments on the generation FLIR to be used and it's suseptability to damage would be greatly appreciated.

  • Author

RQ-2A Pioneer

 

UAVPioneer.jpg

 

Size/Signature: VSmall

Sensors: DS-12 EO/IR "2nd Generation FLIR (Day/Night)".

Frequency: C-band/UHF, Line of Sight: yes, Satellite: no, GPS:yes

Speed: 65kts

Range: 100nm

Ceiling: 15,000 feet

Fuel: 11USG

Endurance 5.0 hours

 

 

I'm going with 2nd Generation FLIR until someone points me to a reference. Home-brewed counter art. I have two mounted and ready to go. Ooh-rah!

  • Author

First attempt...not good.

 

RQ-2A Pioneer scoping out an SA-6b battery in anticipation of a TLAM strike.

 

Straight Flush detects VSmall at 18km (9.7nm). This puts the RQ-2A well within the 5nm needed for its 2nd Generation, even 8nm if we were to consider it 3rd Gen. RQ-2A is flying at 15,000 feet (Med). Pioneer start point is 18.5km (10nm) on a course of 90 degrees.

 

0800.0 – Tactical Turn

Plot: RQ-2A Course 090 Speed 65kts (6km or 3.25nm)

Move: RQ moves from 18.5 (10nm) to 12.5km (6.8nm)

Planned Fire: none

Detection: Straight Flush rolls 96 – No.

Reaction Fire: none

 

0803.0

Plot: RQ course 090, speed 65kts

Move: RQ moves from 12.5km (6.8nm) to 6.5 (3.5nm)

Planned Fire: none

Detection: Straight Flush rolls 74 – Yes. RQ rolls 72 – Yes. Engagement Turns invoked

 

0803.5 (per 2.2.5)

2nd Fire: 2x SA-6b launched

2nd AA Res: none

 

0804.0

1st Move: 2x SA-6 move 12.8km (6.9nm) reaching the RQ. RQ moves 500m to 6.0km (3.2nm)

1st Fire: none

1st AA Res: Gainful ATA 4.0. - RQ DATA 0.5 - RQ VSmall RCS 1.0 = +2.5 ACP = 55%. 06, 99. One hit - that’s all she wrote, “My screen is blue” says the remote operator.

  • Author

I suppose flying it lower, much lower would allow to benefit from the combination of the FLIR not being effected by altitude and the Straight flush's limitation at detecting a/c at VLow/NOE.

 

These seem to have been heavily utilized in DS/DS, with a number lost to enemy action. Does anyone know of the details of say at what altitude these uav's were actually employed?

 

Thanks

Pioneer was used to spot for naval gunfire support for the battleships USS Missouri and USS Wisconsin. I don't know exact operational altitude, but one story goes like this ... the Wisconsin sent her Pioneer low enough to let the Iraqis hear its engine and thus let them know they were about to be shelled in a most unpleasant fashion. The Iraqis surrendered. ;)

  • Author

Interesting report on UAV's

UAV Study B)

  • Author

At the suggestion of Paul K (Av8rMongo) I'm going to amend the pioneer signature stat to "stealthy" and due to the snail like speed add a house rule 50/50 chance that an acquisition radar can lock onto such a small/slow object.

 

I'll run a few trials and report back.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.