319. DebriSat Panel Preparation and Fragment Characterization
Team
| Name | Role | Primary |
| Norm Fitz-Coy | Principal Investigator | ● |
| Paul Wilde | Tech Monitor | ● |
| Tonya Lewis | Fiscal Admin | ● |
Project Description
Space debris presents a major risk to the success of space missions. At orbital velocity, a collision with a fragment as small as 1 cm in size can cause catastrophic damage. Fragmentation debris is of particular importance because it makes up over forty percent of the rapidly increasing number of catalogued objects orbiting the Earth. Satellite breakup models are used to make predictions regarding fragments that are too small to be tracked from the ground, yet are large enough to pose a risk to satellites. However, the 2009 collision between Iridium-33 and Cosmos-2251 demonstrated the need to update the current NASA satellite breakup model. This model, which is based on a hypervelocity impact of a 1960s Navy satellite, failed to accurately predict the debris field produced by the newer Iridium satellite. The failure of the model was attributed to the newer materials and construction techniques used in the fabrication of the Iridium-33 satellite.
The DebriSat project was conceived as a mechanism to update the current satellite breakup model. The DebriSat satellite was a 50-kg satellite designed and fabricated with modern materials and procedures to be representative of satellites found in low Earth orbit (LEO). The DebriSat satellite was subjected to a hypervelocity impact test at Arnold Engineering Development Center (AEDC) where the test chamber was lined with foam panels to preserve the fragments resulting from the impact. These panels were collected and shipped to the University of Florida where they are being processed to extract the fragments which are then characterized and catalogued. This task focuses on the database used to catalogue the fragments.
Project Outcomes
Specific activities include the following:
– Research viable database engines and storage methods.
– Install and configure new database engine.
– Define and document structure of new database engine and subsequent relational tables.
– Begin modification of the existing DCS front-end layer.
– Complete modification of the existing DCS front-end layer.
– Implement new image and file storage structure.
– Begin addition of “3D” imaging system fields and formats.
– Complete addition of “3D” imaging system fields and formats.
– Documentation of upgrade process and maintenance protocols.