This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||
|
REFERENCE FOR COCA-COLA EXPERIMENT:
http://quest.arc.nasa.gov/people/journals/space/kloeris/05-01-01.html —Preceding unsigned comment added by 216.79.146.128 (talk) 15:34, 25 August 2008 (UTC)
What did these magical cola cans look like? How were they designed? —Preceding unsigned comment added by 203.97.255.148 (talk) 09:14, 18 January 2009 (UTC)
The article needs to more prominently cover (e.g. in the intro paragraph) the "limits to inhibit" call during ascent, as this incident makes the mission unique and is extremely notable. There's some source material in "Story: The Way of Water" by Anne E. Lenehan. http://books.google.com/books?id=kFuf9pSnbSYC starting at about page 198. Undoubtedly there's coverage elsewhere too! (sdsds - talk) 17:21, 7 August 2010 (UTC)
It is also note-worthy that this was the first targeted proximity operations mission. Targeting algorithms onboard the Shuttle included Rendezvous (RNDZ) code for coarse orbit adjustment, as well as fine. Coarse adjustments used targeting algorithms that employ Lambert equations. The fine, close-in, adjustments were made with newly tested (at the time) code using Clohessy-Wilshire equations, and using all available sensors in the aft cockpit. These were extensively tested in both 3-DOF and 6-DOF simulators before proximity targeted maneuvers were approved by NASA.
Due to the ATO, the entire mission ops for Days 2 and 3 were replanned real-time. RNDZ orbit designers worked 24 hours straight to replan the targeted proximity operations. This allowed the plasma physics phase of the mission to proceed as planned. — Preceding unsigned comment added by Nataliesees (talk • contribs) 14:59, 14 May 2015 (UTC)
Hello fellow Wikipedians,
I have just modified 2 external links on STS-51-F. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template ((source check))
(last update: 5 June 2024).
Cheers.—InternetArchiveBot (Report bug) 09:40, 11 November 2017 (UTC)
Discovery was used for this mission, not Challenger. Also, why isn't this merged with STS 26? 2600:6C42:7700:3F17:B19C:3019:1D19:D677 (talk) 02:49, 8 March 2021 (UTC)
Clarifying this for future readers, I believe this user confused the [STS-51-F] and [STS-26] missions, both of which used the number '26' as identifiers for their respective missions in official documentation, but they were distinctive missions with different crews, payloads, shuttles, and objectives. For reference, here are two YouTube videos of the launches and landings of these different missions - shown as external links: [STS-51-F] [STS-26R] SpacePod9 (talk) 01:40, 28 January 2022 (UTC)
In the infobox it is shown Perigee altitude 312 km (194 mi) Apogee altitude 320 km (200 mi). In the "Launch" section, it is stated The plan had been for a 385 km (239 mi) by 382 km (237 mi) orbit,[8] but the mission was carried out at 265 km (165 mi) by 262 km (163 mi).[9]. Doesn't this mean the Perigee/Apogee was 265/262 km, not 312/320 km? Or are they different stats? Sijambo (talk) 16:19, 27 November 2023 (UTC)