Bondline - User contributions [en]

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/vendor/wikimedia/at-ease/src/Wikimedia/AtEase/AtEase.php on line 50

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/vendor/wikimedia/at-ease/src/Wikimedia/AtEase/AtEase.php on line 50

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiMain::setContinuationManager(): Implicitly marking parameter $manager as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiMain.php on line 701

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiMain::logRequest(): Implicitly marking parameter $e as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiMain.php on line 1938

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiBase::setContinuationManager(): Implicitly marking parameter $manager as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiBase.php on line 673

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiBase::makeMessage(): Implicitly marking parameter $params as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiBase.php on line 1221

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiBase::errorArrayToStatus(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiBase.php on line 1246

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiBase::addBlockInfoToStatus(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiBase.php on line 1276

Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/includes/exception/MWExceptionHandler.php on line 310

Deprecated: ApiModuleManager::__construct(): Implicitly marking parameter $objectFactory as nullable is deprecated, the explicit nullable type must be used instead in /var/www/bondline1_39_17/includes/api/ApiModuleManager.php on line 62
https://bondline.org/api.php?action=feedcontributions&feedformat=atom&user=Sbw Bondline - User contributions [en] 2026-11-10T23:49:12Z User contributions MediaWiki 1.39.17 https://bondline.org/index.php?title=Auxiliary_Fuel_Tank&diff=4126 Auxiliary Fuel Tank 2022-07-16T17:20:21Z

Sbw: <hr /> <div>There is an STC for an auxiliary fuel tank for Grumman 4-seaters. It is particularly useful for the AA5, which has a 37 gallon fuel capacity in the wing tanks. The STC holder is [http://griggsaircraft.com/ Griggs Aircraft]. The auxiliary fuel tank is an 18 gallon tank that fits in the baggage compartment. It is about 1 1/2 to 2 feet high and covers about 3/4 of the floor space in the baggage compartment. The fuel tank feeds the right wing tank. The fuel transfer must be started manually and can be stopped manually or will stop automatically when the auxiliary tank is pumped dry. (It will not stop automatically if the wing tank is full. Extra fuel will be vented overboard.) A fuel gauge for the auxiliary tank and the transfer switch are mounted just forward of the position of the cigarette lighter on the console between the pilot and copilot seats. It takes approximately 80 minutes to pump the 18 gallon aux tank dry. If you have installed this STC, you must carry a copy of the Form 337 with you in the plane. Otherwise you are liable to have the aux tank disassembled if, for example, a customs or law enforcement officer wants to search your plane and see if you are carrying drugs or other contraband. ---- [[Image:O&N_Tank_Side.jpg]] View from Tiger Cargo Hatch [[Image:O&N_Tank_Top.jpg]] View from Front ----</div>

Sbw https://bondline.org/index.php?title=User_talk:Jlacairetiger&diff=4105 User talk:Jlacairetiger 2022-03-08T22:25:01Z

Sbw: Welcome! <hr /> <div>'''Welcome to ''Bondline''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Sbw|Sbw]] ([[User talk:Sbw|talk]]) 14:25, 8 March 2022 (PST)</div>

Sbw https://bondline.org/index.php?title=User:Jlacairetiger&diff=4104 User:Jlacairetiger 2022-03-08T22:25:01Z

Sbw: Creating user page for new user. <hr /> <div>Tiger owner N74105 KLWM retired USAF</div>

Sbw https://bondline.org/index.php?title=User_talk:Michael.Arcamuzi&diff=4103 User talk:Michael.Arcamuzi 2021-05-26T16:35:07Z

Sbw https://bondline.org/index.php?title=User:Michael.Arcamuzi&diff=4102 User:Michael.Arcamuzi 2021-05-26T16:35:07Z

Sbw: Creating user page for new user. <hr /> <div>I own Grumman AA5A #840. I fly out of the Memphis area.</div>

Sbw https://bondline.org/index.php?title=User_talk:Garygbond&diff=4096 User talk:Garygbond 2021-05-01T15:13:21Z

Sbw: /* Resolved: Problem with Your Image Uploads */ new section <hr /> <div>'''Welcome to ''Bondline''!''' We hope you will contribute much and well. You will probably want to read the [https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents help pages]. Again, welcome and have fun! [[User:Sbw|Sbw]] ([[User talk:Sbw|talk]]) 13:14, 28 April 2021 (PDT) == Resolved: Problem with Your Image Uploads == I noticed Bondline failed to create thumbnails of your uploaded images. I've resolved that problem. Sorry for the difficulty.</div>

Sbw https://bondline.org/index.php?title=User_talk:Garygbond&diff=4082 User talk:Garygbond 2021-04-28T20:14:36Z

Sbw https://bondline.org/index.php?title=User:Garygbond&diff=4081 User:Garygbond 2021-04-28T20:14:36Z

Sbw: Creating user page for new user. <hr /> <div>Private pilot soon to start on instrument rating; I own a 1978 Grumman AA-5B Tiger. In my professional life, I'm a composites materials and process engineer who had a 26-year career with Boeing and now work for a composite material supplier.</div>

Sbw https://bondline.org/index.php?title=AG5B&diff=4080 AG5B 2021-01-13T17:35:06Z

Sbw: <hr /> <div>The AG5B was manufactured from 1990 to 1993 by American General Aircraft company in Greenville, MS, and starting in 2001 by Tiger Aircraft in Martinsburg, West Virginia. It was marketed as the Tiger. The [https://iacra.faa.gov/iacra/AircraftSearch.aspx IACRA] codes for the Tiger are GA-AA-5B and GA-AG-5B. {| class="wikitable" |+AG5B Serial Numbers !Year !First !Last |- |1990||AG5B-09997||AG5B-10009 |- |1991||AG5B-10010||AG5B-10096 |- |1992||AG5B-10097||AG5B-10150 |- |1993||AG5B-10151||AG5B-10178 |- |2001||AG5B-10201||AG5B-xxxx |- |2002||AG5B-xxxx||AG5B-10214 |- |2003||AG5B-10215||AG5B-10230 |- |2004||AG5B-10231||AG5B-xxxx |- |2005||AG5B-xxxx||AG5B-10250 |- |2006||AG5B-10251||AG5B-xxxx |} {| class="wikitable" |+Bondline Contributors Who Own or Fly AG5Bs !Name !Year !SN !N Number !Handle !Country |- |Your Name||Model Year||Serial Number||Tail Number||Your Plane's Nickname||Country |- |[[User:jabley|Joe Abley]]||1992||10127||C-FBLY||None||Canada |- |[[User:Ned_Thomas|Ned Thomas]]||2001||10202||N923TE||None||USA |- |[[User:Mike_Babin|Mike Babin]]||2004||10233||N954TE||None||USA |- |[[User:RFilbey|Russ Filbey]]||2005||10243||N964TE||Silver Sister||USA |} [[Category:Tiger Topics]] [[Category:Tiger Aircraft]]</div>

Sbw https://bondline.org/index.php?title=AA5B&diff=4079 AA5B 2021-01-13T17:34:19Z

Sbw: <hr /> <div>The [http://en.wikipedia.org/wiki/Grumman_American_AA-5#AA-5B_Tiger AA5B Tiger] was manufactured from 1975 to 1979 by Grumman American (later Gulfstream American.) Gulfstream ceased production of all piston-engined aircraft in 1979 and the highly successful Tiger design went out of production after 1,323 aircraft had been delivered. The [https://iacra.faa.gov/iacra/AircraftSearch.aspx IACRA] codes for the Tiger are GA-AA-5B and GA-AG-5B. {| class="wikitable" |+AA5B Serial Numbers !Year !First !Last |- |1975||AA5B-0001||AA5B-0110 |- |1976||AA5B-0111||AA5B-0399 |- |1977||AA5B-0400||AA5B-0692 |- |1978||AA5B-0693||AA5B-0905 |- |1979||AA5B-0906||AA5B-1323 |} {| class="wikitable" |+Bondline Contributors Who Own or Fly AA5Bs !Name !Year !SN !N Number !Handle !City !Country !Notes |- |[[User:Wes_Chapman|Wes Chapman]]||1976||AA5B-0121||N74080|| ||Vidalia, GA||USA|| |- |[[User:9242Z|Kevin Olinger]]||1976||AA5B-0183||N9242Z|| ||Studio City, CA ||USA|| |- |[[User:Radiohound|Frank Sundram]]||1976||AA5B-0194||N200FW|| ||Davenport, IA||USA|| |- |[[User:GregAmy|Greg Amy]]||1977||AA5B-0537||N81140|| ||New Haven, CT ||USA|| |- |[[User:Az_gila|Gil Alexander]]||1977||AA5B-0635||N12GA||Tigger||Tucson, AZ||USA|| was N28478 |- |[[User:Richard Dale|Richard Dale]]||1979||AA5B-0991||VH-IGI||Iggy||Perth||Australia||[http://www.flightclub.com.au Available for hire.] |- |[[User:Hondahaven|David Steward]]||1979||AA5B-1105||N4525P|| ||Memphis, TN||USA|| |- |Brisbane Flying Group||1979||AA5B-1139||VH-WPQ|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |Brisbane Flying Group||1979||AA5B-1238||VH-WPZ|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |Brisbane Flying Group||1979||AA5B-1299||VH-WPM|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |[[User:Jack_Horn|Jack Horn]]||1979||AA5B-1304||N4539S|| ||Houston, TX ||USA|| |} [[Category:Tiger Topics]]</div>

Sbw https://bondline.org/index.php?title=AA5B&diff=4078 AA5B 2021-01-13T17:32:08Z

Sbw: <hr /> <div>The [http://en.wikipedia.org/wiki/Grumman_American_AA-5#AA-5B_Tiger AA5B Tiger] was manufactured from 1975 to 1979 by Grumman American (later Gulfstream American.) Gulfstream ceased production of all piston-engined aircraft in 1979 and the highly successful Tiger design went out of production after 1,323 aircraft had been delivered. The IACRA codes for the Tiger are GA-AA-5B and GA-AG-5B. {| class="wikitable" |+AA5B Serial Numbers !Year !First !Last |- |1975||AA5B-0001||AA5B-0110 |- |1976||AA5B-0111||AA5B-0399 |- |1977||AA5B-0400||AA5B-0692 |- |1978||AA5B-0693||AA5B-0905 |- |1979||AA5B-0906||AA5B-1323 |} {| class="wikitable" |+Bondline Contributors Who Own or Fly AA5Bs !Name !Year !SN !N Number !Handle !City !Country !Notes |- |[[User:Wes_Chapman|Wes Chapman]]||1976||AA5B-0121||N74080|| ||Vidalia, GA||USA|| |- |[[User:9242Z|Kevin Olinger]]||1976||AA5B-0183||N9242Z|| ||Studio City, CA ||USA|| |- |[[User:Radiohound|Frank Sundram]]||1976||AA5B-0194||N200FW|| ||Davenport, IA||USA|| |- |[[User:GregAmy|Greg Amy]]||1977||AA5B-0537||N81140|| ||New Haven, CT ||USA|| |- |[[User:Az_gila|Gil Alexander]]||1977||AA5B-0635||N12GA||Tigger||Tucson, AZ||USA|| was N28478 |- |[[User:Richard Dale|Richard Dale]]||1979||AA5B-0991||VH-IGI||Iggy||Perth||Australia||[http://www.flightclub.com.au Available for hire.] |- |[[User:Hondahaven|David Steward]]||1979||AA5B-1105||N4525P|| ||Memphis, TN||USA|| |- |Brisbane Flying Group||1979||AA5B-1139||VH-WPQ|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |Brisbane Flying Group||1979||AA5B-1238||VH-WPZ|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |Brisbane Flying Group||1979||AA5B-1299||VH-WPM|| ||Brisbane||Australia||[http://www.brisflying.org/ BFG] |- |[[User:Jack_Horn|Jack Horn]]||1979||AA5B-1304||N4539S|| ||Houston, TX ||USA|| |} [[Category:Tiger Topics]]</div>

Sbw https://bondline.org/index.php?title=AA1A&diff=4076 AA1A 2020-09-16T00:20:40Z

Sbw: <hr /> <div>The AA1A was manufactured from 1971 to 1972 by American Aviation in Cleveland, Ohio. It was marketed as the Trainer in 1971, and as the Trainer and the TR-2 in 1972. {| class="wikitable" |+AA1A Serial Numbers !Year !First !Last |- |1971||AA1A-0001||AA1A-0245 |- |1972||AA1A-0246||AA1A-0470 |} {| class="wikitable" |+Bondline Contributors Who Own or Fly AA1As !Name !Year !SN !N Number !Handle |- |[[User:Steve Williams|Steve Williams]]||1971||AA1A-0231||N9431L||[https://sbw.org/flying/#N9431L The Orange Airplane] |- |Marc Sheltra||1971||AA1A-0307||N6307L||[http://www.digitalblast.net/N6307L D-DAY] |- |Ron Walker||1972||AA1A-0414||N706LG||[http://www.airport-data.com/aircraft/photo/060062.html Austin Tx] |}</div>

Sbw https://bondline.org/index.php?title=True_Confessions&diff=4075 True Confessions 2020-09-16T00:18:46Z

Sbw: <hr /> <div>This page is dedicated to allowing pilots to tell their tale of getting away with something that could have cost them their plane, their license, or their life. The postings are intended to be informative, and cautionary to others. The submitter may identify themselves, or post anonymously by allowing one of the moderators to place the text on the page, thus preventing others from looking in the "History" of the Wiki to see who made a particular modification. Please take the stories in the spirit they are offered, that we might all learn from someone's mistake and thus avoid putting ourselves in that position in the future. At the suggestion of one of the submitters, I've rearranged the Confessions so that the most recent one goes at the top. ---- '''Next True Confession Goes Here''' ---- '''Orange Airplane Fuel Starvation Incident''' On April 20, 2003, I had a scary fuel starvation incident flying the orange airplane, my '71 AA1A. [https://sbw.org/fuelfail/ Read the full story] on my web site. ---- '''An Elevating Experience''' After a long weekend, I was returning to my home airport which had a bit of a crosswind. My landing a bit sloppy and I was sure I could do better. So instead of turning to my tie-down area, and despite being tired, I decided to practice crosswind landings. I taxied back and as I started down the runway, something very unusual happened.I lifted off way too early. My airspeed was low but I was climbing like an elevator. I pushed the nose down hard to gain airspeed but continued to climb like crazy. I was sure I set the trim correctly, and verified the indicator was in the takeoff range. However, a quick check out the window confirmed I just took off with Full Flaps. Once I had enough speed I retracted the flaps and landed fine, and on the way back to my car I walked the long way around, avoiding the FBO area in case someone noticed. ---- '''Lost in Colorado''' My private pilot instruction was interrupted by a job transfer from Georgia to Denver Colorado, so I needed more dual instruction to become familiar with a new aircraft and the new terrain. The school plane was an old Warrior that seemed neglected, as most students preferred the newer Cessnas. But I knew I would someday own a Grumman, so I preferred training in planes with the wings mounted correctly, (i.e. low wing). Having worked my way back up to solo, it was time to do my first solo cross country in the area. This would be my first time venturing away from the Denver area, so I picked an airport just 51 miles away (KLIC). There weren't too many landmarks on my course, but I found a small river and a couple of towers that were in my path. A VOR station was right in the middle so I carefully calculated the TO/FROM vectors. In addition, I dutifully worked the winds, magnetic variations, etc. and set off for my first solo cross country in Colorado. I was very pleased with by dead reckoning as the VOR indicator was right in the middle. However I failed to spot any of my landmarks. The river, it turned out, was a dry riverbed and the towers were too small to be distinguished from the landscape. Having passed my midway point, I waited for the VOR indicator to flip as I passed the station. It did not change at all! I checked and double checked the frequency but nothing. I had no landmarks, no VOR and my dead reckoning was off. I was lost! How was I going to find this tiny airport now? Well, I cheated. One week before this flight, I bought a Garmin 296 and stuffed it in my flight bag, just in case. I really did not intend to use it at all, but I sure needed some help. It turned out I wasn't too far off course, but given the lack of landmarks in the area, I probably would have passed right by the destination airport. I later found out that the VOR receiver was inoperable, but the instructor forgot to notify me, and there was no INOP label on the VOR. After that incident, I decided that I would always know the full condition of the aircraft I was flying, and one way to do that is to own the airplane. So just a few weeks later, I bought my first aircraft, a Grumman of course, with a functional VOR, and my trusty 296 mounted on the yoke. ---- '''Should have gone around, but didn't...''' My story also concerns go-arounds - the one I should have made and did not. Soloed but not yet licensed, I'd spent the day practicing crosswind landings. Hopped over to a nearby field, hillier and different terrain than my home field. On descent to the runway, it's rough and wild. Too wild for my skill level. Just before touchdown, correcting for left crosswind, I notice the two windsocks, one at each end of the field, pointing in different directions. Right at touchdown, suddenly it's all from the right. My nose swings hard left as the wheels touch and just like that I'm off the runway, into a shallow field of small boulders separating the taxiway from the runway. A few wild bounces later, somehow without dragging a wing or flipping, the plane bounds out of the boulder field onto the taxiway. The only physical damage was one torn wheelpant. What really suffered was my confidence. After waiting for the winds to subside, I somehow took off and got it home, but resolved never to fly again. Thank God for my mature, experienced instructor. He told me some of his own true confessions, and dogged me to get back in the cockpit. I'm licensed now, and deeply grateful for the chance to keep learning. Many successful go arounds later, I have a healthy respect for crosswinds and for the wisdom of going around. ---- '''There is no shame in a go-around!''' I had just entered the downwind with a bit of extra speed due to merging with a couple of people in the pattern doing touch and go's. On final, I still had a little more speed than usual, but plenty of runway, so no worries. (Some of you already know what happened next). The mains touched down perfectly, and I lowered the nose. Then "bounce", I'm in the air again, (rebound from the nose wheel). Oh no, the dreaded porpoise! My first thought was of my instructor telling me there is no shame in going around. I thought I might have it under control (my bad), but then it bounced again. At this time, the emails I had read on the Gang kicked in. In particular, I remembered reading one "experienced" contributor's email about putting the throttle to the wall in a bad situation and how no face lost in a go around, but much face is lost in a botched landing. So I throttled-up and went around. My daughter was my passenger and she was laughing at the bouncing, "can we do it again". This was much better than me crying over a bent aircraft.</div>

Sbw https://bondline.org/index.php?title=User_talk:GusK&diff=4074 User talk:GusK 2020-07-13T17:53:29Z

Sbw https://bondline.org/index.php?title=User:GusK&diff=4073 User:GusK 2020-07-13T17:53:29Z

Sbw: Creating user page for new user. <hr /> <div>New 1974 Grumman AA1B Owner. Private Pilot working on Instrument Commercial and excited new owner</div>

Sbw https://bondline.org/index.php?title=Bondline:Privacy_policy&diff=4072 Bondline:Privacy policy 2020-06-28T15:47:43Z

Sbw: Added Google CAPTCHA disclosure. <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]]Bondline is provided by volunteers. As such, you visitors and contributors to Bondline should not expect your security or privacy is protected. We do our best, and we have good intentions, but we do not have the resources of more formal organizations. For that reason, Bondline may be less secure than services with more resources or expertise. That might mean Bondline is more likely to disclose information about you that you didn't expect or cause security problems on your computers. That said, we respect your privacy and security, and we have a little expertise in protecting them, so we believe you can use Bondline with confidence. Bondline collects data in several ways: * Bondline logs your visits. Your full IP address is recorded. * If you choose to allow Bondline to run Javascript on your computer, Bondline records a good deal of information about you and your computer. In particular, Bondline tracks each of your visits to the web site as you move from page to page and when you follow links from Bondline to other web sites. Bondline records your operating system, web browser, window size, and lots of other details of your computer's configuration. In practice, that information [https://panopticlick.eff.org/ uniquely identifies your computer], and it may identify you personally. * If you log in to Bondline and contribute, your contributions are linked to your Bondline account for all to see. * We do our best not to disclose your email address directly, but you can choose to allow other logged-in Bondline contributors to send you messages that will be delivered to you by email. * If you choose a Bondline username or register with an email address that's similar to those you use on other web services, it's likely that anyone can guess your username or email address on those other services and so correlate your activity across several web sites. * We do our best not to disclose your password, but mistakes happen. If you use the same password on Bondline as on other web sites, and a data breach occurs on Bondline or elsewhere, it's likely an attacker could pose as you on several web sites. If you use sensitive web sites (your job, bank, or private communications), be sure to know and apply good practices to protect your privacy. Here are a few ways we try to protect your privacy and security: * We use Mediawiki software, the same software used by Wikipedia. That means we benefit from the expertise of many developers around the world. Other open-source software behind Bondline includes Ubuntu, Apache, MySQL, Imagemagick, Memcached, and much more. All of the software behind Bondline is available for inspection by experts, and none of the software is encumbered by licensing or other legal restrictions, as best we can determine. We hope this minimizes the risk that Bondline or you contributors can be victimized by unscrupulous people or organizations. * We keep the software up to date as best we can. That means when vulnerabilities are discovered in the software, they affect Bondline as little as possible. * We don't use third-party services, such as Google Analytics or Facebook "Like" buttons, that routinely track you as you browse the web. Note, however, that we do use Google's CAPTCHA service to reduce spam. We haven't investigated the privacy implications of Google CAPTCHA, but we have confirmed that the Mediawiki software does not track you when you ''read'' Bondline. It is used only when you are first log in to Bondline, and when you submit or edit material. * [[File:serveratsfccp.jpg|200px|thumb|right|Bondline's Server at Monkeybrains's Colo]]Bondline relies as little as possible on commercial internet providers. In its first years, Bondline ran on a server owned by [[User:Sbw|Steve Williams]] installed in a facility operated by [http://monkeybrains.net/ Monkeybrains], a commercial host with a long track record of respecting privacy and pretty good contracts with its commercial landlord and upstream internet access providers. As such, your contributions to Bondline were less likely to be quashed by bogus legal demands, and your use of Bondline was less likely to be disclosed by our providers. Later, Bondline moved to a commercial, shared hosting provider, again one with a good privacy track record. When Steve found out that provider had been sold to GoDaddy, a company known for dubious business practices, he moved Bondline to DigitalOcean, another commercial hosting provider that gives customers like us excellent control over our virtual servers. (Here's a [https://m.do.co/c/40236d4dd6ab referral link to DigitalOcean]. If you use that link open a DigitalOcean account, Steve's account will get a small reward, helping to defray the cost of running Bondline.) Steve almost certainly will be notified of any legal demands before action is taken, and he'll try to contact you before taking action that affects your contributions or your privacy. Where could we do better? * We retain web server logs and web analytics data. It'd probably be better to delete all such logs routinely and often. But we like to know how people use Bondline, and it's harder to do that while aggressively deleting logs. Maybe you have some expertise in this area and would like to help! Please help improve this privacy policy! We want this to be understandable by non-technical visitors and contributors. And we want this to serve as one example of how volunteer projects can be clear about their intentions and give their communities realistic expectations about privacy and security, and maybe even help their community members protect themselves better. (As of January 5, 2011, this document had a Flesch-Kincaid Grade Level of about 11 according to [http://www.addedbytes.com/code/readability-score/ Added Bytes]. A Grade Level of 8 would be preferable, to [http://www.useit.com/alertbox/20050314.html better serve all readers]. If you'd like to take a stab at improving the readability of this page, your efforts are welcome!)</div>

Sbw https://bondline.org/index.php?title=User_talk:Sbw20200627&diff=4071 User talk:Sbw20200627 2020-06-28T00:28:23Z

Sbw https://bondline.org/index.php?title=User:Sbw20200627&diff=4070 User:Sbw20200627 2020-06-28T00:28:23Z

Sbw: Creating user page for new user. <hr /> <div>This is a test of the ConfirmAccount extension after upgrading to Mediawiki 1.34.</div>

Sbw https://bondline.org/index.php?title=Bondline:Privacy_policy&diff=4069 Bondline:Privacy policy 2020-06-28T00:14:00Z

Sbw: <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]]Bondline is provided by volunteers. As such, you visitors and contributors to Bondline should not expect your security or privacy is protected. We do our best, and we have good intentions, but we do not have the resources of more formal organizations. For that reason, Bondline may be less secure than services with more resources or expertise. That might mean Bondline is more likely to disclose information about you that you didn't expect or cause security problems on your computers. That said, we respect your privacy and security, and we have a little expertise in protecting them, so we believe you can use Bondline with confidence. Bondline collects data in several ways: * Bondline logs your visits. Your full IP address is recorded. * If you choose to allow Bondline to run Javascript on your computer, Bondline records a good deal of information about you and your computer. In particular, Bondline tracks each of your visits to the web site as you move from page to page and when you follow links from Bondline to other web sites. Bondline records your operating system, web browser, window size, and lots of other details of your computer's configuration. In practice, that information [https://panopticlick.eff.org/ uniquely identifies your computer], and it may identify you personally. * If you log in to Bondline and contribute, your contributions are linked to your Bondline account for all to see. * We do our best not to disclose your email address directly, but you can choose to allow other logged-in Bondline contributors to send you messages that will be delivered to you by email. * If you choose a Bondline username or register with an email address that's similar to those you use on other web services, it's likely that anyone can guess your username or email address on those other services and so correlate your activity across several web sites. * We do our best not to disclose your password, but mistakes happen. If you use the same password on Bondline as on other web sites, and a data breach occurs on Bondline or elsewhere, it's likely an attacker could pose as you on several web sites. If you use sensitive web sites (your job, bank, or private communications), be sure to know and apply good practices to protect your privacy. Here are a few ways we try to protect your privacy and security: * We use Mediawiki software, the same software used by Wikipedia. That means we benefit from the expertise of many developers around the world. Other open-source software behind Bondline includes Ubuntu, Apache, MySQL, Imagemagick, Memcached, and much more. All of the software behind Bondline is available for inspection by experts, and none of the software is encumbered by licensing or other legal restrictions, as best we can determine. We hope this minimizes the risk that Bondline or you contributors can be victimized by unscrupulous people or organizations. * We keep the software up to date as best we can. That means when vulnerabilities are discovered in the software, they affect Bondline as little as possible. * We don't use third-party services, such as Google Analytics or Facebook "Like" buttons, that routinely track you as you browse the web. * [[File:serveratsfccp.jpg|200px|thumb|right|Bondline's Server at Monkeybrains's Colo]]Bondline relies as little as possible on commercial internet providers. In its first years, Bondline ran on a server owned by [[User:Sbw|Steve Williams]] installed in a facility operated by [http://monkeybrains.net/ Monkeybrains], a commercial host with a long track record of respecting privacy and pretty good contracts with its commercial landlord and upstream internet access providers. As such, your contributions to Bondline were less likely to be quashed by bogus legal demands, and your use of Bondline was less likely to be disclosed by our providers. Later, Bondline moved to a commercial, shared hosting provider, again one with a good privacy track record. When Steve found out that provider had been sold to GoDaddy, a company known for dubious business practices, he moved Bondline to DigitalOcean, another commercial hosting provider that gives customers like us excellent control over our virtual servers. (Here's a [https://m.do.co/c/40236d4dd6ab referral link to DigitalOcean]. If you use that link open a DigitalOcean account, Steve's account will get a small reward, helping to defray the cost of running Bondline.) Steve almost certainly will be notified of any legal demands before action is taken, and he'll try to contact you before taking action that affects your contributions or your privacy. Where could we do better? * We retain web server logs and web analytics data. It'd probably be better to delete all such logs routinely and often. But we like to know how people use Bondline, and it's harder to do that while aggressively deleting logs. Maybe you have some expertise in this area and would like to help! Please help improve this privacy policy! We want this to be understandable by non-technical visitors and contributors. And we want this to serve as one example of how volunteer projects can be clear about their intentions and give their communities realistic expectations about privacy and security, and maybe even help their community members protect themselves better. (As of January 5, 2011, this document had a Flesch-Kincaid Grade Level of about 11 according to [http://www.addedbytes.com/code/readability-score/ Added Bytes]. A Grade Level of 8 would be preferable, to [http://www.useit.com/alertbox/20050314.html better serve all readers]. If you'd like to take a stab at improving the readability of this page, your efforts are welcome!)</div>

Sbw https://bondline.org/index.php?title=File:Alphatest.png&diff=4068 File:Alphatest.png 2020-06-28T00:05:27Z

Sbw: Test upload after upgrade to Mediawiki 1.34. <hr /> <div>== Summary == Test upload after upgrade to Mediawiki 1.34.</div>

Sbw https://bondline.org/index.php?title=User_talk:Nvpatentlawyer&diff=4058 User talk:Nvpatentlawyer 2019-08-08T15:22:25Z

Sbw https://bondline.org/index.php?title=User:Nvpatentlawyer&diff=4057 User:Nvpatentlawyer 2019-08-08T15:22:25Z

Sbw: Creating user page for new user. <hr /> <div>Retired patent attorney. Commercial Instrument Multi Engine Pilot. Have owned a Tiger and a Cougar. Currently own the only AA1-B with a 180 HP O-360 engine.</div>

Sbw https://bondline.org/index.php?title=User_talk:Lilredgrumman&diff=4056 User talk:Lilredgrumman 2019-07-29T20:55:05Z

Sbw https://bondline.org/index.php?title=User:Lilredgrumman&diff=4055 User:Lilredgrumman 2019-07-29T20:55:04Z

Sbw: Creating user page for new user. <hr /> <div>PPL, Instrument Rated, A&P. 1972 AA-1A. Live and work in Central VA running Upward Aviation at KPSK. Stop in sometime!</div>

Sbw https://bondline.org/index.php?title=Bondline:Privacy_policy&diff=4054 Bondline:Privacy policy 2018-10-18T17:20:25Z

Sbw: <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]]Bondline is provided by volunteers. As such, you visitors and contributors to Bondline should not expect your security or privacy is protected. We do our best, and we have good intentions, but we do not have the resources of more formal organizations. For that reason, Bondline may be less secure than services with more resources or expertise. That might mean Bondline is more likely to disclose information about you that you didn't expect or cause security problems on your computers. That said, we respect your privacy and security, and we have a little expertise in protecting them, so we believe you can use Bondline with confidence. Bondline collects data in several ways: * Bondline logs your visits. Your full IP address is recorded. * If you choose to allow Bondline to run Javascript on your computer, Bondline records a good deal of information about you and your computer. In particular, Bondline tracks each of your visits to the web site as you move from page to page and when you follow links from Bondline to other web sites. Bondline records your operating system, web browser, window size, and lots of other details of your computer's configuration. In practice, that information [https://panopticlick.eff.org/ uniquely identifies your computer], and it may identify you personally. * If you log in to Bondline and contribute, your contributions are linked to your Bondline account for all to see. * We do our best not to disclose your email address directly, but you can choose to allow other logged-in Bondline contributors to send you messages that will be delivered to you by email. * If you choose a Bondline username or register with an email address that's similar to those you use on other web services, it's likely that anyone can guess your username or email address on those other services and so correlate your activity across several web sites. * We do our best not to disclose your password, but mistakes happen. If you use the same password on Bondline as on other web sites, and a data breach occurs on Bondline or elsewhere, it's likely an attacker could pose as you on several web sites. If you use sensitive web sites (your job, bank, or private communications), be sure to know and apply good practices to protect your privacy. Here are a few ways we try to protect your privacy and security: * We use Mediawiki software, the same software used by Wikipedia. That means we benefit from the expertise of many developers around the world. Other open-source software behind Bondline includes FreeBSD, Apache, MySQL, Imagemagick, Memcached, and much more. All of the software behind Bondline is available for inspection by experts, and none of the software is encumbered by licensing or other legal restrictions, as best we can determine. We hope this minimizes the risk that Bondline or you contributors can be victimized by unscrupulous people or organizations. * We keep the software up to date as best we can. That means when vulnerabilities are discovered in the software, they affect Bondline as little as possible. * We don't use third-party services, such as Google Analytics or Facebook "Like" buttons, that routinely track you as you browse the web. * [[File:serveratsfccp.jpg|200px|thumb|right|Bondline's Server at Monkeybrains's Colo]]Bondline relies as little as possible on commercial internet providers. In its first years, Bondline ran on a server owned by [[User:Sbw|Steve Williams]] installed in a facility operated by [http://monkeybrains.net/ Monkeybrains], a commercial host with a long track record of respecting privacy and pretty good contracts with its commercial landlord and upstream internet access providers. As such, your contributions to Bondline were less likely to be quashed by bogus legal demands, and your use of Bondline was less likely to be disclosed by our providers. Later, Bondline moved to a commercial, shared hosting provider, again one with a good privacy track record. When Steve found out that provider had been sold to GoDaddy, a company known for dubious business practices, he moved Bondline to DigitalOcean, another commercial hosting provider that gives customers like us excellent control over our virtual servers. (Here's a [https://m.do.co/c/40236d4dd6ab referral link to DigitalOcean]. If you use that link open a DigitalOcean account, Steve's account will get a small reward, helping to defray the cost of running Bondline.) Steve almost certainly will be notified of any legal demands before action is taken, and he'll try to contact you before taking action that affects your contributions or your privacy. Where could we do better? * We retain web server logs and web analytics data. It'd probably be better to delete all such logs routinely and often. But we like to know how people use Bondline, and it's harder to do that while aggressively deleting logs. Maybe you have some expertise in this area and would like to help! Please help improve this privacy policy! We want this to be understandable by non-technical visitors and contributors. And we want this to serve as one example of how volunteer projects can be clear about their intentions and give their communities realistic expectations about privacy and security, and maybe even help their community members protect themselves better. (As of January 5, 2011, this document had a Flesch-Kincaid Grade Level of about 11 according to [http://www.addedbytes.com/code/readability-score/ Added Bytes]. A Grade Level of 8 would be preferable, to [http://www.useit.com/alertbox/20050314.html better serve all readers]. If you'd like to take a stab at improving the readability of this page, your efforts are welcome!)</div>

Sbw https://bondline.org/index.php?title=User:Sbw&diff=4053 User:Sbw 2018-10-18T14:04:16Z

Sbw: <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]] [https://sbw.org/ Steve Williams] is the sysop of Bondline. He was the owner of N9431L, a '71 AA1A based at Oakland, California (OAK). His many travels in the orange airplane are recorded in his [http://mira.sbw.org/photos/ photo blog]. Steve purchased the orange airplane from Jon Maestre in 1996. Jon said the orange airplane was the first Grumman he owned. Steve was the editor and electronic services director of [http://www.aya.org/ AYA] from 1995 to 2004. Steve sold the orange airplane in 2018, having moved on to sailing and road cycling. He continues to operate Bondline in support of Grumman owners and pilots.</div>

Sbw https://bondline.org/index.php?title=User:Sbw&diff=4052 User:Sbw 2018-10-18T04:30:57Z

Sbw: <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]] [https://sbw.org/ Steve Williams] is the sysop of Bondline. He was the owner of N9431L, a '71 AA1A based at Oakland, California (OAK). His many travels in the orange airplane are recorded in his [http://mira.sbw.org/photos/ photo blog]. Steve purchased the orange airplane from Jon Maestre in 1996. Jon said the orange airplane was the first Grumman he owned. Steve was the editor and electronic services director of [http://www.aya.org/ AYA] from 1995 to 2004. Steve sold the orange airplane in 2012, having moved on to sailing and road cycling. He continues to operate Bondline in support of Grumman owners and pilots.</div>

Sbw https://bondline.org/index.php?title=User:Sbw&diff=4051 User:Sbw 2018-10-18T04:28:40Z

Sbw: <hr /> <div>[[File:Sbwgbrwide.jpg|200px|thumb|right|Bondline Sysop Steve Williams]] [http://www.sbw.org/ Steve Williams] is the sysop of Bondline. He was the owner of N9431L, a '71 AA1A based at Oakland, California (OAK). His many travels in the orange airplane are recorded in his [http://mira.sbw.org/photos/ photo blog]. Steve purchased the orange airplane from Jon Maestre in 1996. Jon said the orange airplane was the first Grumman he owned. Steve was the editor and electronic services director of [http://www.aya.org/ AYA] from 1995 to 2004. Steve sold the orange airplane in 2012, having moved on to sailing and road cycling. He continues to operate Bondline in support of Grumman owners and pilots.</div>

Sbw https://bondline.org/index.php?title=User_talk:Jdellamorte&diff=4049 User talk:Jdellamorte 2018-08-04T13:04:53Z

Sbw https://bondline.org/index.php?title=User:Jdellamorte&diff=4048 User:Jdellamorte 2018-08-04T13:04:53Z

Sbw: Creating user page for new user. <hr /> <div>Co Owner of Tiger N1536R PPSMEL</div>

Sbw https://bondline.org/index.php?title=User_talk:Jfalcon20&diff=4047 User talk:Jfalcon20 2018-05-11T14:21:48Z

Sbw: Welcome! <hr /> <div>'''Welcome to ''Bondline''!''' We hope you will contribute much and well. You will probably want to read the [[https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents|help pages]]. Again, welcome and have fun! [[User:Sbw|Sbw]] ([[User talk:Sbw|talk]]) 14:21, 11 May 2018 (UTC)</div>

Sbw https://bondline.org/index.php?title=User:Jfalcon20&diff=4046 User:Jfalcon20 2018-05-11T14:21:48Z

Sbw: Creating user page for new user. <hr /> <div>Jeff Anderson Michigan Falcon 10 Type rating, ATP. Been flying since 1987, my first airplane purchase 3 months ago was a 1974 Traveler, N9526L I’ve been in Aviation as a career since November of 1987 when I started as a Flight Follower for a local 135 Air carrier. I spent 13 years in Grand Rapids working for an ari carrier and moved back to Ann Arbor 3 years ago.</div>

Sbw https://bondline.org/index.php?title=Talk:AG5B&diff=4043 Talk:AG5B 2018-01-23T01:30:25Z

Sbw: <hr /> <div>Why is it AA-1A, AA-5B, etc. and yet its AG5B? They are all listed on the Type Certificate with a dash in the model. The only time there is no dash between the letters and number is in the serial number. Then the convention is AA1-0001 or AG5B-10001. --Bob Steward It's my fault. When I began editing the AYA ''Star'' in 1995, I observed that the convention there seemed to be no dash, and I've continued that for all this time. I wanted to be consistent, and anyway, it looks better in print. I realize some of the official documents use the dash. --sbw Sorry if I stamped on some prior decision by eliminating the top (non-title) row in the second table -- it just looked like a duplicate of the heading row to me. Might it not be reasonable to replace the title row with the text below it if that text is preferred? -jabley The purpose of the second line is to encourage people to fill in their information. But I'm open to suggestions for how to do that better. - sbw</div>

Sbw https://bondline.org/index.php?title=AG5B&diff=4041 AG5B 2018-01-23T00:43:25Z

Sbw: <hr /> <div>The AG5B was manufactured from 1990 to 1993 by American General Aircraft company in Greenville, MS, and starting in 2001 by Tiger Aircraft in Martinsburg, West Virginia. It was marketed as the Tiger. {| class="wikitable" |+AG5B Serial Numbers !Year !First !Last |- |1990||AG5B-09997||AG5B-10009 |- |1991||AG5B-10010||AG5B-10096 |- |1992||AG5B-10097||AG5B-10150 |- |1993||AG5B-10151||AG5B-10178 |- |2001||AG5B-10201||AG5B-xxxx |- |2002||AG5B-xxxx||AG5B-10214 |- |2003||AG5B-10215||AG5B-10230 |- |2004||AG5B-10231||AG5B-xxxx |- |2005||AG5B-xxxx||AG5B-10250 |- |2006||AG5B-10251||AG5B-xxxx |} {| class="wikitable" |+Bondline Contributors Who Own or Fly AG5Bs !Name !Year !SN !N Number !Handle !Country |- |Your Name||Model Year||Serial Number||Tail Number||Your Plane's Nickname||Country |- |[[User:jabley|Joe Abley]]||1992||10127||C-FBLY||None||Canada |- |[[User:Ned_Thomas|Ned Thomas]]||2001||10202||N923TE||None||USA |- |[[User:Mike_Babin|Mike Babin]]||2004||10233||N954TE||None||USA |- |[[User:RFilbey|Russ Filbey]]||2005||10243||N964TE||Silver Sister||USA |} [[Category:Tiger Topics]] [[Category:Tiger Aircraft]]</div>

Sbw https://bondline.org/index.php?title=User_talk:Jabley&diff=4033 User talk:Jabley 2018-01-22T16:01:39Z

Sbw https://bondline.org/index.php?title=User:Jabley&diff=4032 User:Jabley 2018-01-22T16:01:08Z

Sbw: Creating user page for new user. <hr /> <div>A citizen of the Commonwealth, Joe has variously lived in New Zealand and the UK and currently finds himself inexplicably in small-town Canada, a strange outcome that he hopes one day to remedy. Joe owns and flies AG-5B C-FBLY out of CYXU. The flying in that part of the world is at least very good.</div>

Sbw https://bondline.org/index.php?title=User_talk:Grumman13&diff=4031 User talk:Grumman13 2017-12-15T01:57:30Z

Sbw https://bondline.org/index.php?title=User:Grumman13&diff=4030 User:Grumman13 2017-12-15T01:57:30Z

Sbw: Creating user page for new user. <hr /> <div>I have been flying for just over 30 years. During this time, I flew many general aviation aircraft including tail-wheel aircraft. I first flew a Grumman AA1C in 1985 during my Cross Country Phase of my Private Pilot Training. The Yankee series are great airplanes. I currently fly professionally and wish to fly for fun again with the Canopy slightly open. I am hoping to eventually own a Grumman Yankee Series Airplane with the 20Gal Aux tanks for the occasional solo cross-country flight during the retirement years. I currently have ATP rating and have MEI/CFII and currently reside in the Chicago area.</div>

Sbw https://bondline.org/index.php?title=User_talk:Robertpallen&diff=4027 User talk:Robertpallen 2017-04-17T13:35:25Z

Sbw https://bondline.org/index.php?title=User:Robertpallen&diff=4026 User:Robertpallen 2017-04-17T13:34:55Z

Sbw: Creating user page for new user. <hr /> <div>Single engine land instrument rated Private Pilot with greater than 1000 hrs PIC aspiring to be a Tiger owner. Most of my flying has been through club memberships, but I owned a 1946 7AC Aeronca Champ for a number of years. At this time I am in the information gathering stage of my Tiger endeavor, but I hope to make an acquisition in the next few months-- if I can locate a suitable Tiger at an affordable price. I presently own a hangar at KAKH (Gastonia, NC), live in the Charlotte, NC area, and most of my flying has been done in the midwest and southeast.</div>

Sbw https://bondline.org/index.php?title=User_talk:Pkuhns&diff=4025 User talk:Pkuhns 2017-04-17T13:32:30Z

Sbw https://bondline.org/index.php?title=User:Pkuhns&diff=4024 User:Pkuhns 2017-04-17T13:31:59Z

Sbw: Creating user page for new user. <hr /> <div>Full-time employed, young family, Cheetah (AA5A) owner since early 2011. Perform owner-assisted annuals every year at 'airplane camp' in Rensselaer Indiana (Excel-Air). Replaced the engine in 2013 at a special two-week airplane camp. Love the Cheetah although it could be a little faster. Live in Indianapolis.</div>

Sbw https://bondline.org/index.php?title=User_talk:Dvidoli&diff=4020 User talk:Dvidoli 2016-11-27T20:20:34Z

Sbw https://bondline.org/index.php?title=User:Dvidoli&diff=4019 User:Dvidoli 2016-11-27T20:20:02Z

Sbw: Creating user page for new user. <hr /> <div>Started flying in 1974 in a PA 11 Piper Cub out of a 1400' grass strip in Westboro Ma. After soloing the Cub, transitioned to a PA-28-140 and began flying out of Bridgeport / Sikorsky airport where I completed my private in 1975. Over the years have flown a variety of Piper, Cessna, Beech and other aircraft for my personal enjoyment. I stopped flying in 1986 while starting a business, with a pledge to myself to eventually get back to flying. In 2011 I made good on my pledge and returned to flying this time in a Grumman, with the aim to finally pursue my Instrument.</div>

Sbw https://bondline.org/index.php?title=User_talk:Montana_Rose&diff=4018 User talk:Montana Rose 2016-05-15T18:13:57Z

Sbw https://bondline.org/index.php?title=User:Montana_Rose&diff=4017 User:Montana Rose 2016-05-15T18:13:57Z

Sbw: Creating user page for new user. <hr /> <div>I was widowed when my husband and brother-in-law lost their lives in a 1977 Grumman Cheetah. Years later I learned of faulty carburetors yet NTSB stated on report pilot error and that plane burned. Later the remains of the crash were discovered whereby the fuselage ,carburetor and a significant amount of wreckage remained. (flat ground 1 mile from takeoff.) Research reveals that particular carburetor was faulty and had an Airworthiness directive issued on it. I have copies of the directive and will be taking it to Western Skyways in Montrose, Colorado for inspection. If in fact it malfunctioned as described in the directive I have been counseled to first file suit against NTSB for concealment.Then move forward and file against Marvel Schebler mfg. I was only 27 at time of crash. I have raised our two children and it has not been easy. I am interested in chatting with anyone who may have heard of fatalities in these carbs? NTSB site reports include 30 fatalities with same take off and crash descriptions all of which are chalked up to pilot error. I can provide exact carb info etc if I hear from someone who is familiar with the this topic. I would also appreciate knowing if anyone knows a business that is located closer to me than Western Skyways in Montrose, Colorado. I am in western Montana and the private plane maintenance business here thinks it may be the closest. None in Seattle etc. Not sure if this is appropriate site for this but am trying to network with plane enthusiasts. Thanks for your time and consideration.</div>

Sbw https://bondline.org/index.php?title=User_talk:Travismike30&diff=4016 User talk:Travismike30 2016-02-10T13:29:33Z

Sbw https://bondline.org/index.php?title=User:Travismike30&diff=4015 User:Travismike30 2016-02-10T13:29:33Z

Sbw: Creating user page for new user. <hr /> <div>My name is Mike. I just bought my first Grumman Traveler. I've had a Cessna 172 for the last eight years. I came across a good deal on the Grumman that I couldn't pass up. It needs some work, since it has been sitting for a few years. I joined this sight to get some help with the repairs that are needed.</div>

Sbw https://bondline.org/index.php?title=User_talk:Rollawade&diff=4005 User talk:Rollawade 2015-12-03T14:58:34Z

Sbw https://bondline.org/index.php?title=User:Rollawade&diff=4004 User:Rollawade 2015-12-03T14:58:34Z

Sbw: Creating user page for new user. <hr /> <div>Owner of 1972 AA5 since 1975. It has taken me to the 4 corners of the US and made several round trips from Tennessee to the west coast. I seek to keep it maintained cost effectively by working closely with my local IA to perform maintenance overseen by him when required. I am hoping to gain information and possibly do the installation of the required ADS-B in the future.</div>

Sbw
Deprecated: Constant E_STRICT is deprecated since 8.4, the error level was removed in /var/www/bondline1_39_17/vendor/wikimedia/at-ease/src/Wikimedia/AtEase/AtEase.php on line 50