Since we’ve started shipping FlightBox kits, I figured it was time to put up some instructions. The goal has always been to keep the process as simple and quick as possible. I’ve timed myself, and I can assemble a Dual Band FlightBox in about 4 minutes. A friend who agreed to act as a guinea pig took about 15 minutes, and he was using only the printed Assembly Guide. Based on his feedback and input from a number of other helpful reviewers, I tweaked the guide to make a few steps even clearer.
We also now have an Assembly Tutorial video that should help those who prefer to learn visually:
It’s permanent home is here: https://www.openflightsolutions.com/flightbox/tutorial/
Last Friday evening I had the honor and privilege of giving a presentation on ADS-B, Stratux, and FlightBox at VAA Chapter 16 in Gardner Kansas. The talk covered all the basics of ADS-B In and Out, as well as an introduction to Stratux and FlightBox. There were something like 30 – 40 people at the meeting, and they seemed to like the presentation, so I’ve decided to share a PDF of it for anyone who’s interested. They devoted over two hours of their weekend, asked a lot of good questions that I hope to wrap up into an FAQ, and in general were great hosts and a wonderful audience. (I ended up joining the chapter – $20 well spent.)
ADS-B is confusing: two system (UAT / 1090) and two function (out / in). I hope this helps clear up some of the questions. Please let me know if you would like a live presentation – I really enjoy meeting people and geeking out on all-things aviation.
Tonight I’m going to be giving a talk on ADS-B, Stratux, and FlightBox at VAA (Vintage Aircraft Association) Chapter 16 in Gardner, Kansas. The talk is entitled “ADS-B For Everyone” and it includes a primer on ADS-B, a review of available options, an overview of the Stratux project, and a brief introduction to FlightBox. Gardner is within a few miles of the ADS-B ground tower at New Century airport (KIXD), so I hope to be able to do a live demo of weather and traffic.
I’ll update this post with a copy of the slides after the presentation.
Wow. It’s hard to believe that it’s already March 8. An amazing amount has happened in the past six weeks. The Kickstarter launched, reached its minimum goal, and concluded. We launched a new web store (huge thanks to Shopify for making that relatively painless). We endured the agonizing two week wait for the money from Kickstarter. We ordered another $20,000+ in parts using personal credit cards. Last Thursday the Kickstarter funds finally arrived. (Yay!) Today we got confirmation that the last of the major components – the wifi adapters and Raspberry Pis – have shipped.
Last week the VK-172 USB GPS modules arrived – in full retail packaging. My wife and daughter helped me remove them from the packaging, then “shell” them – removing the plastic housing. I now have a box containing 500 GPSs, all tested to make sure that they boot. A random sampling of roughly 10% have been tested to make sure that they achieve a 3D GPS lock. So far – kudos to the nameless Chinese company who makes the VK-172 – they’ve all passed.
This past weekend was all about the fans. The 40mm x 10mm cooling fans arrived (as expected) without a connector. I spent several hours trimming, stripping, crimping and shrouding. (It really is far less sexy than it sounds.) At this point I have about 100 of the 1000 fans prepped for use in FlightBox. If there’s anything that intimidates me about this process it’s the thought of another 900 fans, waiting to be trimmed, stripped, crimped and shrouded. This is going to take a while. Fortunately, it’s the kind of work you can do in front of the TV in the evening.
The next few weeks look to include much of the same. But… I went ahead and booked an AirBNB and a rental car for Fun-N-Sun. It’s about 9 hours flight time from KC to Lakeland in the Tiger, and I’m looking forward to it. We’ve arranged to exhibit as a partner in the Avilution / Droid EFB booth. Sun-N-Fun is good pre for the madness of Oshkosh, so it will give me some idea of what to expect. If you’re going to be at the show, please stop by and say hello. I’ll be demoing FlightBox, talking Stratux, and (if we have any units in stock), selling kits. It should be a good time.
For everyone who’s ordered through the Kickstarter or on the web store prior to now – we expect to ship your FlightBox kit in March. Keep an eye on this blog and / or the Kickstarter updates page for the latest. Thanks to everyone for their enthusiasm and their patience. We’re doing our best to get you an outstanding product as quickly as we can.
We’re coming to the end of the Kickstarter campaign. Hard to believe that 30 days have gone by so quickly. Even harder to believe that we’re at 302 backers. In a final push, we bought the leaderboard on the AOPA Aviation eBrief for today, which has added some 13 new backers in the past few hours. (Thanks, AOPA!) This puts us nearly 7 times our original goal.
If you don’t/didn’t get in on the Kickstarter, be sure to check out the web store. It will open shortly after the campaign ends.
The fabricator of the cases sent another round of production prototypes out today. They should be here on Thursday, and pictures will be posted on the Kickstarter as soon as we get them. This shipment includes another copy of the original light gray and a darker “medium” gray. When the campaign closes and we can do surveys of the backers we will most likely offer a choice between the light and the medium. The light is very light (it looks white to me). The medium is supposed to be significantly… grayer. There are advantages and disadvantages to each. The light reflects more heat, but produces more glare. The medium is the opposite. (Yep, everything really is a compromise.)
The weather is supposed to be good this weekend, so we hope to get some flight testing done with the new boxes and the latest version of the software. It contains the first cut at the update process. We’ve made good progress on a number of other fronts. We now have a good means of making the data card read-only, which significantly reduces the possibility of corruption. We’ve also put together a script which assigns a unique ID to the Wifi SSID of each FlightBox. It’s rare that you would have several operating in close proximity, but not unheard of. This will make that much easier to manage.
That’s it for now. Please check back on Thursday (2/18/2016) to see how the campaign turned out.
We have about a week left on the Kickstarter campaign, which is rather amazing – time flies. In preparation for “what comes next” we’ve started building out a web store that will take over when the Kickstarter ends. We will be offering both models of the FlightBox quick-build kit, plus the FlightBox case for those DIY-ers who want to build a system from scratch.
We’ve already placed an order for first run of cases and will be ordering the other components as soon as the Kickstarter funds arrive. If you’re interested in getting a FlightBox as soon as possible, please place an order on Kickstarter now – the kits will be shipped in “backer order” until all Kickstarter orders have been fulfilled. Only after those have been handled will we be able to process and ship web store orders.
A few days ago Congress published a bill generally referred to as the “FAA reauthorization” – a 279 page document that allocates funding for the FAA for the next several years and also sets policy mandates for the FAA and the Department of Transportation. Formally know as the “Aviation Innovation, Reform, and Reauthorization Act of 2016”, the bill makes some major changes to ATC and includes a number of significant positives for general aviation, including the long sought 3rd class medical reform.
The reauth bill includes provisions that would effectively eliminate the current 3rd class medical requirement within 180 days of enactment. It would allow any pilot with a valid driver’s license to carry up to five passengers in aircraft weighing up to 6000 pounds, on flights below 14,000′ MSL and at speeds below 250 knots. To qualify, the pilot would be required to take a free online medical education course every two years.
This is a bit different from the changes covered in the Pilot’s Bill of Rights 2 that was recently passed by the Senate. That bill required a 3rd class medical for new pilots, and for any pilot who had not held a valid medical certificate within the past ten years. It also limited operations to aircraft weighing less than 6000 pounds, but set the ceiling slightly higher at 18,000′ MSL. It also mandated a checkup by a primary care physician every four years. While it’s hard to predict the future, it’s quite likely that the reauth will eventually be rewritten to match the PBOR2 simply to reduce friction.
Much like the PBOR2, the language in the reauth gives the FAA 180 days to produce rules that meet the intent of the law. If they fail to meet that deadline, the law explicitly prohibits them from taking any action against pilots who operate within the specified limitations without a medical. This is one of the few places where the bill actually adds teeth. Other sections set deadlines for changes but do not include any penalty that automatically triggers if the Administrator fails to meet it.
(edit: added weight limit, removed John Travolta joke)
The biggest change outlined in the bill is a controversial plan to move air traffic services away from the FAA and into a stand-alone not-for-profit “ATC Corporation”. (Catchy name, eh?) The GA alphabet organizations (AOPA, EAA, NBAA) have long been opposed to this for fear that the change would result in user fees being levied for use of ATC services. Anticipating that objection, the bill prohibits user fees for piston and non-commercial turbine aircraft:
(c)(4) Charges and fees may not be imposed for air traffic services provided with respect to—
(A) aircraft operations of piston engine aircraft; or
(B) noncommercial aircraft operations of turbine engine aircraft.
Why they chose to make this distinction by propulsion technology is something of a mystery. If the goal is to carve out GA and only charge commercial carriers, it would seem logical to specify who pays based on the operating rules. “Only those flight operations conducted under Part 121 or Part 135 are subject to user fees.” or similar.
The bill also specifically prohibits the new ATC Corporation from giving preferential access to airspace based on who’s a paying customer. Specifically:
(d) Access To Airspace.—Neither the amount of charges and fees paid nor the applicability of subsection (c)(4) shall be determinant of access to airspace.
Those two provisions would seem to place GA in a pretty solid spot, but the devil is always in the details. AOPA appears to be taking a cautious wait-and-see approach, while EAA’s initial take on the bill notes concerns about the limited level of input available to GA and the potential for a “money talks” reality in a privatized world. The difference in the response may well be attributable to the way that the governance system for the proposed corporation is structured. The board would be made up of 11 individuals with 2 representing GA. The two would be selected thusly:
(4) 2 Directors nominated by the Nominating Member appointed by the principal organization representing noncommercial owners and recreational operators of general aviation aircraft.
The “Nominating Member” – the individual appointed to the nominating committee for the board – will be selected as follows:
(B) An individual appointed by the principal organization representing noncommercial owners and recreational operators of general aviation aircraft.
And here you see the potential for a turf battle. Which group is “the principal organization representing noncommercial owners and recreational operators“? Is that the AOPA or the EAA? Who gets to make the decision?
(b) Determination Of Principal Organizations.—
(1) BEFORE DATE OF TRANSFER.—Before the date of transfer, and not later than 30 days after the date of enactment of this subtitle, the Secretary shall determine the principal organizations referred to in subsection (a)(2).
(2) AFTER DATE OF TRANSFER.—On and after the date of transfer, the Board shall determine the principal organizations referred to in subsection (a)(2) in accordance with the bylaws of the Corporation.
So for the initial period, the decision gets made by the Secretary of the Department of Transportation. I’m a member of both AOPA and EAA and believe strongly in the good done by both organizations. That said I’m almost certain that the Secretary will select AOPA as the “Principal Organization” – it represents a broader swath of the private GA world than EAA. (I would personally love to see them work together on this, but power has an interesting effect on organizational dynamics.)
The bill specifically hands the nominating membership and the board seats to the “principal organization representing noncommercial owners and recreational operators of general aviation aircraft” so what about Business Aviation? As it stands now, they and a bunch of other groups get seats at the kids’ table. The bill provides for a board of advisors that includes BizAv, airport operators, the Department of Defense, aerospace manufacturers and other groups that may have an interest in air traffic.
To be honest, as long as I can fly when and where I want without being nickeled and dimed, I don’t personally care if ATC is a function of an agency or of a federally chartered private corporation. Perhaps I’m naive, but the governance structure is irrelevant to me. Anyone out there have a good counterargument? Am I missing something?
For the past several years there has been some argument over whether a tenant at an airport that receives federal funds can use that space to build an airplane. At question is whether or not construction of a homebuilt aircraft qualifies as an “aeronautical activity”. While it should seem obvious to any reasonable person that building an aircraft is at least as “aeronautical” as storing one, some bonehead airport administrators have used it as an opportunity to push out homebuilders in favor – presumably – of tenants that buy more fuel.
The reauth bill put those dastardly plans asunder by defining building a recreational aircraft as a duly aeronautical activity:
“(1) IN GENERAL.—The construction of a covered aircraft shall be treated as an aeronautical activity for purposes of—
“(A) determining an airport’s compliance with a grant assurance made under this section or any other provision of law; and
“(B) the receipt of Federal financial assistance for airport development.
Note that “covered aircraft” in this case means “covered by this law” – it does not mean that it only applies to the Polyfiber crowd. Hopefully that will put an end to one of the more silly aeronautical kerfuffles of the recent era.
If you’ve read any of the articles that I’ve written (other than the one about how my ailerons froze on takeoff once), you probably know that I have a personal passion for hacking through the red tape that makes it impossible (or at least economically unfeasible) to upgrade legacy aircraft with safety-enhancing modern technology. It seems that Congress feels the same way. The reauth bill includes a small but vital section that attempts to force the FAA to finally get over its fear of computers and allow us to retrofit our aircraft in ways that make sense.
(a) Policy.—Not later than 180 days after the date of enactment of this Act, the Administrator of the FAA shall establish and begin implementation of a risk-based policy that streamlines the installation of safety enhancing equipment and systems for small general aviation airplanes in a manner that reduces regulatory delays and significantly improves safety.
(b) Inclusion Of Certain Equipment And Systems.—The safety enhancing equipment and systems for small general aviation airplanes referred to in subsection (a) shall include, at a minimum, the replacement or retrofit of primary flight displays, auto pilots (sic), engine monitors, and navigation equipment. [emphasis added]
(c) Collaboration.—In carrying out this section, the Administrator shall collaborate with general aviation operators, general aviation manufacturers, and appropriate FAA labor groups, including representatives of FAA aviation safety inspectors and aviation safety engineers certified under section 7111 of title 5, United States Code.
(d) Small General Aviation Airplane Defined.—In this section, the term “small general aviation airplane” means an airplane—
(1) that is certified to the standards of part 23 of title 14, Code of Federal Regulations;
(2) has a seating capacity of fewer than 9 passengers; and
(3) is not used in scheduled passenger-carrying operations under part 121 or 135 of title 14, Code of Federal Regulations.
This is exactly what I’ve been looking for. Unfortunately, I don’t think the policy wonks who wrote this have a very solid understanding of the actual requirements and processes – things like TSO authorization, STCs, etc. – that stand in the way of this. This is rather an expansion of the language from the General Aviation Revitalization Act from 2013 which demanded that the FAA have had the complete Part 23 rewrite complete by December 15, 2015. That day came and went and so far as I can tell, nobody was fired, demoted, or even publicly humiliated for the failure.
What this needs is some teeth – a bit like the medical provision included. It should say that if the Administrator fails to act by the deadline set in the statute then owners of applicable aircraft may begin operating them under the regulations that currently govern Experimental Amateur Built aircraft without threat of enforcement for violation of current airworthiness regulations. (Statutes always trump regs. Yay statutes!) I’m not holding my breath, but I have to guess that this would get things rolling.
The bill attempts to get some motion on a wholesale improvement in the torturously slow and complicated process of certifying new aircraft. It creates a new advisory committee at the DoT (rather than FAA) level that is tasked with reviewing the FAA’s current certification process and providing suggestions for improvement. This is essentially what the Part 23 ARC did for Part 23 certification back in 2012, but apparently congress wants this to be an ongoing effort.
Specific efforts outlined in this section include a comprehensive review of the FAA’s current engineering designee program with an eye towards expanding it and giving DERs greater autonomy. The bill also calls for an emphasis on risk-based (as in “risk continuum”) regulation rather than the current “one size fits all” approach. With any luck this will all flow in with the Part 23 rewrite to result in a much smarter process for certifying GA aircraft.
There’s a hand-wavy section that calls for the Administrator to approve the use of unleaded avgas as soon as the Administrator decides that there’s a suitable replacement. It does include a specific demand that once a suitable drop-in replacement is found the FAA:
(3) adopts a process (other than the traditional means of certification) to allow eligible aircraft and engines to operate using qualified replacement unleaded gasoline in a manner that ensures safety.
I interpret that as a demand to skip the per-model STC process for certification and simply offer a blanket approval for any aircraft that currently burns 100LL. This seems kind of obvious. Hopefully the deadline (again, imposed without any teeth) will help make unleaded gas a reality sooner rather than later.
There’s a provision in the bill that would require the FAA and the ATC Corporation provide a means to hide the registration number of private aircraft at the owner’s request. This is probably well intentioned, but a combination of direct ADS-B and the public record registration database (which includes ICAO codes) makes this pointless.
The bill calls for the creation of a GA-lead task force to review the FAA’s current rules for Part 91 operation. In general the task force is charged with looking for ways to improve processes related to the bureaucratic minutia handled by the FAA: letters of authorization, delegation to appropriate designees, methods for training FAA personnel. In general this sounds like yet another attempt to reform the culture of CYA that’s endemic a the agency. The Part 23 ARC report blamed the majority of the issues with certification on the internal culture. This expands that to encompass more than just the ACO.
A final bone tossed to us: they want to expand the registration period for aircraft to 10 years. Sounds good to me.
Tort Reform – The price of new aircraft will not come down until we get blanket tort reform. The bill should make all lawsuits involving aircraft federal. It should also define private aviation as an inherently risky activity. Better still – cap the recovery from any GA accident at $1m (the amount covered by most GA insurance policies). THAT would help revive GA.
Teeth – Every provision in that bill that has a deadline should have a section outlining the repercussions that will automatically occur should the agency fail to meet it. That’s the only thing that will make it move at anything more than its traditional, glacial pace.
Here’s a link to the full text for anyone who’s interested: https://www.congress.gov/bill/114th-congress/house-bill/4441/text
The production prototype case arrived last week while I was out of town for a conference. It was actually a bit frustrating knowing that it was sitting on my desk at home – I’ve been looking forward to seeing it ever since we finalized the design. When I got home late last Thursday but took a few minutes to unpack, take a look at the build quality, and do a quick fitting. The result: almost perfect on the first try. Here it is assembled:
The Pi fits perfectly, with the power connector and audio jack exposed. It screws to the “bosses” – the standoffs with integrated nuts – perfectly using ordinary 1/4 #4 screws. I might add a lock washer and go up to 3/8″ to avoid the screws backing out due to vibration. The SDRs and GPS fit just fine, with the GPS being locked in place by the far-end wall of the case. The SMA pigtails hold the SDRs in place and exit the case on the opposite end. The fan, which bolts to the top, also fits very cleanly.
The one adjustment that’s required is a small notch in one mounting cleat on the top. It’s just a bit too thick to slide in beside the Edimax wifi module, so it needs to be trimmed. This actually works out perfectly as it then prevents the module from backing out. The fabricator will be able to make the adjustment at no additional charge (yay!) and without it impacting the delivery date. Here are a few shots of the inside of the case:
I’m duly impressed with the quality of both the build and the material. The case looks great and the Boltaron is very strong. It fits together very tightly – to the point where it feels like a solid block, rather than a plastic box with parts inside. Perhaps that’s a cliche, but it’s also true. The one minor disappointment I have is with the color. I picked “light gray” and this is it… very light. The next option is “medium gray” which is much darker. I may offer buyers the option of light or medium. I need to order a medium gray and make sure it doesn’t have any heat issues.
A final note: several people have asked about future upgrades. Here’s a shot of the FlightBox with a development shield installed:
The shield (or is it a HAT?) fits perfectly inside the case, but it will require a new top as the fan will need to be moved up to make room for the board and any components mounted on it. We will probably offer two options for the upgrade: one is just the card and it will require you to move the fan to the outside of the case; the other is a new top that makes room for the board and the fan inside.
One other detail to point out: note the holes at the end of the case right by the SDRs. Those are lined up perfectly with the MCX connectors so that you can connect an MCX cable directly with the module should you wish. Most people will prefer to use the SMA jacks – they provide a much more solid connection – in which case the holes offer a direct source of airflow over the SDRs.
Question: do you the fabricator to add holes in the bottom for permanent mounting? Let me know what you think.
We launched our Kickstarter on Tuesday night. The campaign is running for 30 days. The goal was $10,000. I was guessing it would take at least a week to get there. We hit the $10k mark about 30 hours in. As I write this – just over two full days into the campaign – we’re at $14,625 – 146% of goal and still climbing.
Thanks to everyone who’s backed us. This is a great start to what I hope will be an amazing journey. I can’t believe that I have to wait another 28 days to know how the crowdfunding experiment turns out.
If you’re interested in owning a FlightBox, please take a look at the Kickstarter page. We’ve sold out of the early bird for dual-band but we still have a few early bird single-bands, and an unlimited number of both at the regular price.
This week the National Transportation Safety Board (NTSB) released its annual “Most Wanted” list – a catalog of ten transportation safety improvements that they want to prioritize for the next year. For the fourth year in a row, general aviation accidents – specifically, loss of control accidents – remained on the list. (Considering that all GA accidents kill roughly 300 people each year – compared with 5,000 motorcyclists and 25,000 motorists – you would think the NTSB would find richer targets for improvement. But I digress…) I have a suggestion for them. If they want to do something about GA accidents, they should ask their friends at the FAA to radically revise the certification requirements for retrofit upgrades.
That might sound a bit odd, so let me explain my thinking.
First, we have to recognize that loss of control accidents are a people problem: Pilots who haven’t flown but a few hours in the past several years who suddenly get a bug to fly into Oshkosh. Pilots who don’t think they need to go through transition training for their shiny new airplane. Pilots who have flown the same mission so many times that they think they can make a perfect landing while texting. To put it bluntly, you can’t fix stupid – and we’re all stupid at some point. The lucky ones survive it.
So if you can’t fix people, what can you fix?
Better technology is one of several factors that have all but eliminated accidents in commercial aviation. Upgrading the GA fleet with a limited amount of automation which could prevent a loss of control accident is easily within our technical grasp. The problem is not the technology, but access to that technology. The current regulations make it economically infeasible to upgrade certified airplanes. The FAA knows this, but thus far has only been able to take baby steps to remedy the situation.
Last year saw the release of Memorandum authorizing the installation of basic, stand-alone angle of attack (AoA) indicators. The installation is automatically deemed to be a minor modification thus avoiding the need for an STC. This is definitely a step in the right direction. AoA provides a much more accurate view of the airplane’s available lift. Unfortunately, as with the other baby step on digital attitude indicators, the AoA must not connect with or provide data to any other system. “Here’s some really useful data but it can only go to this little display on the glareshield.” WTF, FAA?
What we really need is inexpensive “envelope protection” – the industry term for the sort of automation that could detect and avoid an impending stall. Envelope protection requires that aircraft be retrofitted with a computer system commonly called an Electronic Flight Information System or EFIS. The EFIS processes data from various sensors – airspeed, AoA, GPS, AHRS – and sends commands to the autopilot and (some day soon) the autothrottle. In the event of an incipient stall, the EFIS would first warn the pilot, then enact a recovery procedure if the pilot does not react in time. It may sound overbearing, but it might also save your life.
At this time there are only a handful of manufacturers who offer retrofit EFIS solutions for certified airplanes. Garmin. Avidyne. Bendix King. Aspen. These system start out at $20k and can easily cost as much as $150k. It would be difficult to justify pouring $20k for an Aspen into my Grumman Tiger. I can’t imagine anyone putting that kind of money into a Cessna 150 or a Piper Cherokee. The low end of GA is effectively locked out of potentially life-saving upgrades based on cost.
The high cost of upgrades is largely based on the certification and approval requirements. Manufacturers must use design assurance and validation processes created for the air transport industry. They must follow an arcane process (DO-178C) that effectively prohibits the use of off-the-shelf open source operating systems. The certification process for something like an EFIS can easily add millions to the cost of development. All of these processes and testing requirements are mandated in the name of safety, but the result is actually the opposite: most GA aircraft are stuck in 1970s.
Compounding the frustration is the fact that an EFIS for a GA airplane does not have to cost a great deal. There are several very capable and very well tested systems available for the Experimental and LSA markets that could easily evolve to offer envelope protection. Products from Dynon, MGL, Advanced, TruTrak and even Garmin have all the necessary sensors and processing power to save lives, but are “not presently authorized” (in the words of FAA chief Michael Huerta) for use in certified GA aircraft.
If the NTSB wants to save the lives of GA pilots and passengers, it should look next door and ask the FAA to expedite the guidance changes that will allow affordable safety-enhancing technology to reach the market. It’s either that or find a way to fix stupid.