ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

Treasure!

Updated on August 21, 2015

Treasure! -- Context

The story Treasure! was written following a vacation to Michigan. We had stopped by my sisters to see their new house on the lake and enjoy some time together. My brother-in-law, who is mostly kid himself, had hidden a 'treasure' on the island in their back yard. When the kids heard about it they decided it was time to take out a canoe and go on the hunt.

When we got back to Maryland I wrote this story, added a treasure map, and sent a copy back for their enjoyment. I took the events of the day, added some descriptive names, and colored in the details. The result is a memorable story about an event my kids enjoyed with their cousins, and I hope it will stay with them for years to come.

Treasure! -- The Story Begins

The sun was falling into the western sky. The treasure seekers reviewed the final clues, took a radio from the mission director, and pushed Discovery from the dock. With swift, sure strokes they glided through the calm water, over the sandy bottom, and toward their goal.

This evening was the culmination of intense planning and good fortune. The team came together from as far away as Maryland synchronizing their visits and covering their intentions with stories providing perfect alibis. Somewhere 'attending graduation parties', others 'on vacation'. They had arranged a casual dinner near the site then excused themselves after the main course with just enough time to make a run for it. The host and other dinner guests never suspected anything unusual, and if things went just right they would be back in time for dessert.

Treasure! -- The Hunt

On the hunt....

Helmsman set a course for the leeward side of the island where they would beach Discovery and stage for the push around the southern coastline. At the bow was Power Stroke, a paddler who was dragging the team forward with each pull. Amid-ships Map Master and Tactician were putting finishing touches on the plan. After an intense discussion it was settled. They would travel light, and when they reached site papa tango two they would push inland following previously discovered clues towards the target.

They arrived without incident, right on schedule. The landing zone was quiet and they got ashore with out being spotted. After securing Discovery and their gear they started hiking. While on the move they carefully observed their surroundings for any signs that the mission had been compromised. Fortunately all was clear. They arrived at papa tango one without incident but had some problems finding the trail towards the next way-point.

The team spread out looking for the trail. Map Master found telltale signs of a path and they were off again. Finally, papa tango two -- dead ahead. The team started marking off the clues then begin a grid pattern search. They continued for what seemed an eternity. No dice. The team split, one squad going back to the LZ for dual use paddle/spade gear while the other squad continued the search. When the squads came back together they risked breaking radio silence for additional support from the mission director. More searching. Running out of time. Painfully, a decision to abort.

The team slumped back to the boat and paddled back to the docks. The timing was good and the hosts didn't catch on. They would have one more try, and desert was magnificent. Home made strawberry/rhubarb and raspberry/blueberry pie, outstanding.

Treasure! -- Another Try

Later that night, during the mission hot wash, the team surfaced several ideas for a second attempt. Now that the route was mapped Helmsman and Power Stroke could be swapped for more effective search capability reinforced with heavy equipment and sapping expertise. By adding Diviner and Sapper the team would have a good chance of success with only a minimal increase of risk.

The day dawned cool with a hint of rain and whispers of mist floating on the waters. The newly constituted team boarded Discovery and pointed towards the LZ. They arrived without incident and Diviner homed in on the target with guidance from Map Master. Sapper kicked off the dig with #2 heavy and within minutes Tactician lit up the airwaves with a success report.

The trip back was uneventful. The team split the treasure, and with teary farewells parted company to return to their mundane undercover roles. Stay tuned for the next adventure, rumor has it that it may be the Allegheny wilderness!

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://corp.maven.io/privacy-policy

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)