LE-X

edit

It is very unlikely the LE-X would be designated LE-7B; it is a totally different design. More likely it would be designated LE-9, as given in the infobox. 69.72.92.165 (talk) 01:57, 26 March 2015 (UTC)Reply

Name

edit

Now the official name is H3 Launch Vehicle.[Name 1] Note that it uses Arabic instead of Roman numeral, with no hyphen. Fukumoto (talk) 13:34, 2 July 2015 (UTC)Reply

References

edit
  1. ^ "Announcement of the Official Naming of the Next Generation Launch Vehicle". JAXA. July 2, 2015. Retrieved July 2, 2015.

First launch

edit

The introduction states that the first launch would be without solid-rocket boosters in 2020 but Planned launches lists the first launch as H3-22S with 2 SRBs. 96.88.198.77 (talk) 03:37, 21 January 2020 (UTC)Reply

Updated. Please take a look. --Fukumoto (talk) 12:21, 21 January 2020 (UTC)Reply

A Commons file used on this page or its Wikidata item has been nominated for deletion

edit

The following Wikimedia Commons file used on this page or its Wikidata item has been nominated for deletion:

Participate in the deletion discussion at the nomination page. —Community Tech bot (talk) 11:07, 5 April 2022 (UTC)Reply

Launch dates often mean the relevant Japanese fiscal year which ends the following March

edit

Launch dates often mean the relevant Japanese fiscal year which ends the following March, So "in 2022" means by "end March 2023". - Rod57 (talk) 15:55, 12 April 2022 (UTC)Reply

Inmarsat signed up for an early launch, but what satellite and mass

edit

Future launches shows Inmarsat as first non-Japanese payload/customer. but what satellite and mass ? Maybe the Inmarsat-6 F2 ? (Inmarsat-6_F1 was 5,470 kg) - Rod57 (talk) 11:35, 4 May 2022 (UTC)Reply

Need more columns in H3 Launch History table

edit

Need more columns in H3 Launch History table, as in List_of_H-II_series_and_H3_launches#2024 - Can we transclude just H3 rows from there ? or just add 2 columns here, at least payload mass, and orbit payload released into ? - Rod57 (talk) 14:31, 1 July 2024 (UTC)Reply