Questions about the mission.

Instrument sets vary by mission. The Spring 2026 research includes temperature, pressure, humidity, carbon dioxide, ultraviolet channels, particulate channels, and Geiger count rate. A channel name describes what was recorded; its units, calibration, and mounting determine what conclusions it can support. The research figures explain those limits alongside the plots.

In the team’s payload configuration, the UV sensors are attached to the outside faces and wired back to the PCB; they are not mounted directly on that board. Their position matters: rotation, shading, and the angle of sunlight can change the response. The Spring 2026 UVA figure averages four side-mounted sensors. See the UV figure.

Air pressure falls with altitude, allowing the balloon’s gas to expand. Temperature generally falls through the troposphere but does not keep falling throughout the stratosphere. A sensor inside the payload also responds to its enclosure and electronics, so it should not automatically be treated as outside air temperature. NASA’s atmosphere model ↗

Start with both axis labels, units, and the caption. Elapsed time is not altitude. GPS altitude, pressure-derived altitude, and a fitted altitude curve are different products. Separate recorders also need verified clock alignment before their readings can be paired. On the data page, read the measurement notes before comparing peaks.

The payload returns through a different place at a later time. Sensor response time, airflow, sunlight, and orientation may also change. Separate the flight phases and compare like units at comparable altitudes. A difference is a research question, not proof of a particular atmospheric effect. Test the possible explanations against instrument behavior and flight context.

Counts per minute describe detected events, not a person’s radiation dose. Detector response and calibration matter. A device’s converted dose-rate field is not an independently validated dosimeter reading. The team’s radiation figures should be read as instrument observations, not used to make health or exposure claims.

No. The report’s UVA, UVB, and UVC channels are not established as calibrated irradiance, UV Index, or exposure dose. A nonzero UVC channel alone does not demonstrate atmospheric UVC: spectral response and cross-sensitivity need review. Read the UVC figure’s interpretation before treating a signal as a physical conclusion.

Not without checking the measurement first. The source reports use inconsistent particulate unit labels, and the website does not silently convert them. Particle counts and mass concentration are not interchangeable. Calibration, airflow, and operation at low pressure must be understood before comparing those channels with air-quality limits. See the particulate figure notes.

Choose something the instruments can distinguish. For example: does sensor orientation explain a UV change, or does temperature response lag differ between ascent and descent? These are proposed questions, not reported findings. Define the comparison, check calibration, keep units and timing consistent, and state what would count against your explanation.

The team tests the assembled payload, checks recording and power, and prepares for flight operations with program partners. Arizona Near Space Research supports ASCEND launches and recovery. After recovery, students inspect the hardware, examine the recordings, and present what worked and what needs another test. ASCEND flight operations ↗

Weather and winds affect launch conditions, the balloon’s path, and where the payload may land. Recovery also depends on terrain and safe access. A published date is a plan, not a guarantee. Use the official ASCEND schedule and flight updates for current information.

Start with the year-by-year missions, then explore the research archive, flight figures, and flight videos. A design abstract describes an investigation; a results figure shows reported observations. Read each item in that context rather than treating every proposal as a flown experiment.

Public research figures, photographed boards, summaries, and footage help explain the team’s work. Original datasets, working documents, analysis scripts, private contact details, and code repositories are not published here. The HTML, CSS, and JavaScript delivered to a visitor’s browser remain inspectable, as on any public website.