Dear SBAG community,
A few SBAG announcements:
Draft Findings from the SBAG 15 Meeting
Thank you for a productive SBAG 15 meeting! A draft document with findings from the meeting is now posted online and available for comments from the SBAG community. Please provide any comments by July 25, 2016. Comments can be emailed to: [email protected] or any SBAG steering committee member.
Request for CubeSat and Small Sat Mission Concepts
As mentioned at the SBAG 15 meeting, we would like to collect a bit of information about possible CubeSat and small sat missions of interest to the SBAG community. We saw a few examples presented by the NIAC fellows at the SBAG 15 meeting and would like to hear your thoughts on the subject. If you?d like, please provide one paragraph briefly describing the following:
? A CubeSat or small sat mission concept (what is to be accomplished and briefly how),
? The benefits of using CubeSats or small sats (e.g. low cost, distributed reach, etc),
? Any technology that would enable or benefit the CubeSat portion of the mission.
Multiple submissions are fine, the CubeSat/small sats can be the primary spacecraft or daughter craft, and notional concepts are fine. We will use this information to augment the newly created SBAG technology roadmap and to respond to any NASA inquiries about the suitability of CubeSat and small sat missions to our community. No proprietary information, please, as the summaries may be posted to SBAG’s website as references for our technology roadmap.
Responses to Carolyn Mercer ([email protected]) by July 22 would be particularly helpful, but we will also collect this information through August 31.
Upcoming SBAG Meetings
January 11-13, 2017
University of Arizona
SBAG 17 tentatively planned for:
June 13-15, 2017
NASA Goddard Space Flight Center
In particular, we’d like to know if there are known conflicts or issues with the dates tentatively planned for the SBAG 17 meeting, as we will be finalizing the dates for this meeting later this month. Please email incoming SBAG chair Tim Swindle ([email protected]) with any known issues or comments.