Fighter Perimeter - Valet Parking?

Posted on Saturday 20 August 2016 @ 04:27 by Commander Save'ena (Sav) Tillatix & Captain John "Apollo" Barstow, M.D. & Captain Melody Jones & Lieutenant Commander David Tan & Warrant Officer Farida Alleen
Edited on on Tuesday 13 September 2016 @ 23:15

Mission: Old, New Ship
Location: Inside Hayes Proving Ground - 200 KKlick Perimeter
Timeline: MD7 - Late Evening
2961 words - 5.9 OF Standard Post Measure

ON:

The Fighters, in continuously dodging asteroids and sending the data back to Merlin, now had a choreograph of the dance most of the asteroids were doing. This made their patrol more into ship detection than harried dodging. There was still the whizz by ones that were had not been tracked yet, but those kept the pilots frosty in looking for those while waiting for the Merlin's long range sensors to let them know about incoming. The Merlin's sensors had much better long range, while the fighters had outstanding close range and speed of intercept, hence why they were out there, to stop any incoming ship at the perimeter.

Sav was using this time to send instructions to the individual pilots for specific asteroid targeting and training firing to help hone skills. By doing this now, they could get the jitters out of the pilots for that initial encounter. =/\= Dragon twenty five, incoming HPG-3145B incoming, small bump on far side of it, that your target. Send sensor logs when done. Dragon Actual Out.=/\=

Sav wanted to see how the new pilots were faring. The initial changeover of pilots at the four hour point went well, Dragon 13, 14, 23, 24, and 32 all being changed out for 15, 16, 25, 26, and 33. Dragons 34, 35, and 36 were on Dashit, the discovery Asteroid, with 36 being used as shield duty if, and only if, a ship got through the perimeter. With those dragon in stealth on the planet, and the discovery ship being such low power, nobody incoming would find it unless they got right on top of it, which was what was wanted. The time counter still showed another two hours before the experienced fighter shift changes, which also meant her. Time to check in with the Merlin.

=/\= Merlin Tac-Ops, Dragon Actual, how goes it? Anybody coming to the party yet? =/\=

Melody responded from the bridge =/\= Dragon Actual, Merlin here. Nothing yet, however all the EM interference from the various asteroids is playing hell with our Sensors. Keep your eyes peeled out there. =/\=

... David was listening to the comm traffic in the Tactical Information Center, he heard the Flight Control Officer reply and scanned his eyes around the large view-screens ... Apart from the Merlin, and the myriad of fighters, there was nothing else on the long-range sensors. He asked for the three-dimensional view to be projected in the middle of the two story Tactical Information Center. In the middle was the ship, countless meteors, of varying sizes and orbital idiosyncrasies, were showing in grey, while the Tri'jema was up in green and the focus of their mission at this point in time. The fighters were orange, moving in what to the untrained eye would seem totally random patterns, but he knew that Melody had choreographed their individual roles throughout this task ... He opened a Comm to Sav:

=^= Tan to Saveena .. Nothing on long-range sensors .. If the Vulcan vessel is coming direct it should enter sensor range on a heading of .. 245.65 .. .. .. I will contact you the second it comes into range .. Tan out =^=

He closed the Comm, and had the panoramic projection shut down, it wasn't needed for everyday usage, but was an excellent tool for allowing an all-round perspective of the state of play when required. Relaying his information to the Bridge he then instructed the estimated heading to be put up on one of the view-screens. he wanted to be ready once the Vulcan's arrived, and wanted to give the Chief of Flight Operations every second to prepare.

Out in Dragon Actual, Sav sent back an answering chirp, and then kept that channel on override. Thus, whatever the fighters were chatting about at the time would be interrupted by anything coming back from the Merlin.

On the command channel, chatter was about Camelot, the runabouts for the mission to 'Dashit', launching. Sav tracked the two incoming.

=/\= Dragon Actual, Dragon two, Camelot is launching, permission to go provide escort?" Wolf asked as he and his wingman circled the area, listening to all the chatter and keeping an eye on his sensors. =/\=

=/\= Dragon Two, Dragon Actual, go ahead and intercept Camelot at 180 KKlicks, escort to 50 KKlicks when Dragons 33 and 34 will finish the escort, then get back to inner perimeter parking. Copy. =/\=

=/\= Copy Actual,=/\= Wolf replied and pressed his left foot against the peddle and pulled back and left on the flight stick, causing his ventral and starboard thrusters to fire while he pulled back to one quarter impulse until he was facing the run about and pushed his throttle back to full impulse.

Dragon's 2 and 26 intercepted the incoming Runabouts. They proceeded across the 150kklick space to meet up with Dragon's 33 and 34 from Dashit.

=/\= Dragon Actual, Dragon 33, thanks for the escort by Dragon 2 and 26. We have Camelot now. Dragon 33 out. =/\=

=/\= Dragon 33, Dragon Actual, Copy that. Dragon 2 and 26, let me know when your back on Perimeter. Dragon Actual out. =/\=

Johnson grinned, Sav was holding her own and he knew the Air Group was in good hands, and that he'd not be needed there after this sortie, =/\= Copy, Actual, time to waypoint is two mikes. =/\=

However, right at the exchange, was the peaceful interlude of dodging asteroids and playing tag tag with surface features come to an end. The usual mission 95% of quiet time was getting ready to be interrupted by that pesky 5% terror time of call to action.

=/\= Dragon Actual and Two, Dragon Three here. I am picking up fluctuations out near the Merlin, Tachyon band. =/\=

=/\= Dragon Pilots, Dragon Actual, not a drill. Possible Bogey near Merlin. Dragons Twenty Two and Twenty Five, rush and cover, you're up. Dragon's 2 and 26, continue to station.=/\=

Dragons 2, 22, 25, and 26 were the fighters circling at 100 KKlicks from the Asteroid. Their job, where-ever a ship was coming in at, was to quickly rush out the the sector with the lone fighter to make a three fighter front. As Dragon's 2 and 26 had done escort service, it was Dragon's 22 and 25 turn to do the support. As Merlin was out of the asteroid field at sector heading 1, it was Dragon 3 they were going to support.

The raptor was light at the controls and had been a front line interceptor for many a decade. Despite many upgrades they had been showing their age, but at least the one Farida flew now was one of the later block models unlike those at pilot training. "Dragon actual, Dragon Twenty two, understood burning to target." the call was simple and while burning was not the navy most commonly used therm, it should be clear enough as she hit full speed.

David was reviewing the topography of the meteors within the cordon when one of his Staff shouted !

"Lieutenant. Tachyon surge, Starboard side, Aft Quarter ... Vessel de-cloaking !" David sat bolt upright as the image on the screen directly in front of him changed sickeningly to show a Mogai-class Warbird. Ordering the shields back to full configuration he focused several of the forward scanning array's on the new arrival.

"Divert 'ALL' non-essential power to the shields and weapons, the Bridge may need them sooner than we thought." he stood, looking at the impressive vessel, seemingly hanging off their right and slightly ahead of the Merlin, "Establish a continuous communications link with the Bridge, we may not have time minutes from now."

"Sir, they have contacted the Bridge." the Ensign informed him, as surprised as David himself.

"Get that Comm link established .... Run continuous scans, above and below us and out to the edge of the asteroid field, I want to know if they have company before they do !" Tan ordered .....

=/\= Merlin Tac-Ops, Dragon Actual, I have two Raptors closing fast to shore up the Broadsword near the Merlin. If you need them and the Broadsword to come for 'Escort' fly by, just give the word. Otherwise, they will stay in Perimeter Defense. =/\=

=^= Dragon Actual .. Tac-Ops .. I am happy with the current situation .. Despite the unannounced arrival .. My concern is their wish to converse .. I would suggest moving at least two of your Raptors .. If available .. To approach the Romulan vessel slowly to see if they jump .. If they are not alone this could be the diversion they planned to have us concentrate on the obvious .. I'm happy to leave the details to your discretion Dragon Actual .. We are scanning as best we can concentrating on the tachyon frequency we picked up before our friend de-cloaked so hopefully we wont have anymore surprises .. I would like someone approaching that vessel just as a gesture but I will defer to your experience CAG =^= Tan waited, eyes flicking between screens as he watched the almost tiny fighters .....

In Sav's fighter, the priority circuit cut in over the Dragons chatter on their setups and alert about the new player in the area. She listened, and responded, =/\= Tac Ops, Dragon Actual, I will have Dragon's 22 and 25 do a flyby to scan the bogey with weapons not active. That way they know were checking them out, yet won't start an incident. Dragon Actual Out. =/\=

It was at this time that Dragon's 33 and 34 responded. =/\= Dragon Actual, Dragon 33, package has been delivered. Dragon 33 out.=/\= Sav sent a com beep in return, and then send a mission update to Merlin Tac-Ops the the runabouts had landed by having a status indicator turn from yellow to green. This was done just in case somebody had managed to crack the rotating codes and were listening in now that they were no longer under cloak.

Keying over to the fighter channel, Sav sent out instructions. =/\= Dragons 22 and 25, Dragon Actual, move on past Dragon 3 and perform a flyover of Merlin and then around Bogey, full scans, weapons passive only. We wanna let them know we are here, but not engage them yet. Copy.=/\=

... David watched the main view-screen and the ominous Romulan War-bird at it's center. There was still the nagging feeling at the back of his mind that they might be here in the open as a diversion of some kind. Where they attempting to covertly secret someone aboard the Tri'Jema ? ... He eyed the other screens:

"Ensign, re-task one of our sensor array's to focus on the found vessel. look for anything out of the ordinary."

"You believe they may attack it Lieutenant ?" the woman asked as she followed orders.

"I have absolutely no idea to be perfectly honest, but I've learned not to openly trust on faith. It may be nothing but better to be safe than sorry." he said, leaning back, asking for a comm to be opened to Sav:

=^= Dragon Actual .. Tac-Ops .. Understood .. I see your fighters .. Tan out =^= ...

"Dragon actual, Dragon Twenty two understood, buzz the target and light her up with senors, but no weapons." Farida said, despite her best effort she could not keep the tension out of her voice. There was danger and there was danger and right now things where serious.

The two raptors made their move flying much more slowly than either of the pilots liked, but in order to not be to threatening and to get the best sensor sweep they had little choice.

"Dragon actual, Dragon Twenty two, sweep in 10 seconds, feeding data directly to mom." Farida said. Mom was indicating the Merlin which was acting as the fighter's mothership.

=/\= Dragon 22, Dragon Actual, confirmed. Keep yourself frosty, just in case.=/\=

... The first sign of the Vulcan's arrival was when the long-range sensors chirped a warning. The quadrant was instantly reassigned to the largest of the view-screens available to Lt. Tan.

Wolf and his wingman circled the 100 KKlick area, listening to all the chatter and keeping an eye on their sensors. They were the only two circling Raptors for ship defense, and there was supposed to be a Vulcan ship coming in soon. And, 'speak of the devil', Wolf keyed his comm, =/\= Merlin, be advised, another tango inbound.....my sensors read the power signature as Vulcan, please confirm and advise.=/\=

Sav caught the direct communication by Wolf. He was in quadrant 4, which was Valkyrie 16's sector 6, other side of Merlin. It seemed the Vulcan ship was keeping the Merlin between it and the Romulan ship. =/\= Dragon 16, Dragon Actual, quit paying attention to the first Bogey and scan for a second, your sector.=/\=

=/\= Merlin Tac Ops, Dragon 16, confirmed on the incoming Vulcan Signature. Bogey two is keeping the Merlin between them and Bogey one. Do you copy. =/\=

=^= Dragon 16 .. Tac-Ops .. Copy that I have it on long range .. They appear to be taking their time coming in .. It is possible they are aware we have people on or in close proximity to the Tri'jema despite their instructions =^= ...

There, still at maximum distance, the Vulcan vessel dropped from warp. It approached on a vector almost identical to the one David had given the Commander Air Group. He opened a comm to Sav:

=^= Dragon Actual .. Merlin Tac-Ops .. Vulcan vessel on heading .. 245.65 .. They have dropped from warp and are approaching under impulse .. No contact at this point .. is it possible to send someone out to the far side of the asteroid field but keep them relatively hidden .. We don't want to give them any excuse to come charging in here but we need positive confirmation that they are not doing anything untoward on their approach =^=

He watched the massive Vulcan ship on screen as he waited for Sav ....

=/\= Merlin Tac-Ops, Dragon Actual, Confirmed. Dragons 15 and 16 will go that way with Talon 2. That will provide full scanning link with Merlin by Talon 2. Dragon Actual will move up into sector facing 6 to replace Dragon 16. Dragons 15 and 16 will become extreme range sector facings 4 and 5 protection. We don't want to launch any relief fighters to take their place from Merlin as that may be seen as an act of war. I will inform when they are in position. Dragon Actual out.=/\=

Melody was also monitoring the fighters comm chatter. "Captain, Dragon is moving to investigate."

... In the Tactical Information Center, David was reviewing the scant information on the anomalous emissions. It was clear that something was approaching the location of the fallen Star Ship. With the Captain now conversing with the Romulan Commander, his sense that their wanting to speak to the Merlin at all was only as a diversion, one which they 'must' know could never have succeeded. One of his staff had concentrated a sensor array on the anomalous emissions and it was clear that whatever they were, they were moving, albeit very slowly, possibly hoping to hide their drive output by almost drifting from asteroid to asteroid as they closed on the Tri'Jema ... He opened a Comm to the fighter Group:

=^= Dragon Actual .. Merlin Tac-ops .. URGENT .. URGENT .. .. Be aware .. Five unidentified energy sources .. Quadrant 2 - Heading 72 mark 18 distance 300 kilometers and closing .. Possible incoming hostiles .. Intercept immediately for investigation and possible contact .. Recommend moving runabouts back to safe distance =^=

Waiting for the Commander Air group to assign Raptors to investigate the anomalous emissions, he began looking at the situation from a new perspective: Rather than the Tri'Jema and the Merlin being hemmed in, he looked at it like they were the center of a sphere, with fighters located at the northern and southernmost points, they were covered should either of the other vessels choose to approach from above or below Zee. The majority of the fighters were now holding an almost circular pattern throughout the three sixty degree perimeter. so effectively, the Merlin was at the center of an imaginary orb, surrounded by erratically drifting boulders of various sizes, and because of this the ship had to constantly make minute adjustments to her relative position within that orb .. With regards to the Vulcan and Romulan vessels, they had, albeit reluctantly, and with the urging of the nearby Raptors, extended the distance between them and the Merlin and were now approximately two hundred kilometers away. Sav's Raptors were holding station one hundred meters from the bow of each vessel. At this stage it was impossible to imagine either races would risk a fire-fight, but that was all dependent on exactly 'what' was hiding in the stranded Tri'Jema ...

=/\= Dragons 2, 26, head to sector facing 5 and go outbound. Mother is reporting Five incoming energy sources via Talon One link up. Tap into Talon One ECM Link and go find them. I am sending Dragon 33 out with you. Dragon 34 and Dragon Actual will have your six and quick support if needed. Dragon 36 will remain hidden at Dashit to provide Shields and fire support when necessary. Copy =/\=

=/\= Two copies, going outbound at sector five,=/\= Richard called and pulled up the Talon sensor feed tie in on his left LCARs screen, =/\=I have the bogies on my scopes, flight, staggered formation,=/\= he called to 26 and 33 as they formed up with him.

=/\= Merin Tac-Ops, Dragon Actual. Dragons 2, 26, and 33 heading out towards signatures. They are linking with Talon One to see exactly what your seeing. Dragons 34 and Actual will be fast support if warranted. Copy. =/\=

... =^= Dragon Actual .. Merlin Tac-Ops .. .. Copy your last .. Readings show target is still approaching though very slowly .. Plot is showing numerous asteroids are converging in the sector .. There will be sporadic blind spots but the rocks should will pass through without collision .. .. Caution is advised as they may be trying to draw your fighters into a bottleneck .. I am tasking sensors to cover =^= ... He sat watching on a secondary screen as the conversation between commander Barstow and the Romulan Commander was played out. He still couldn't shake the feeling that they were not going to allow the Merlin free reign for too long, and would eventually begin to make a harsher, and more worrisome stance ! ...



TBC in Part 2............



OFF:

Major Richard "Wolf" Johnson (APB Barstow)
Longwing's TAD Squadron Commander
USS Merlin

Lieutenant jg. David Tan
Chief Operations Officer
USS Merlin

Lieutenant Melody Jones
Chief flight control officer / Second officer
USS Merlin

Lieutenant jg. Saveena Tillatix
CAG/Uroboros Squadron Leader
Bridge Command Specialist
USS Merlin