| This is the talk page for discussing improvements to the Mount Washington article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
| Archives: 1Auto-archiving period: 6 months |
| This article is written in American English, which has its own spelling conventions (center, color, defense, realize, traveled) and some terms may be different or absent from other varieties of English. According to the relevant style guide, this should not be changed without broad consensus. |
| Mount Washington has been listed as one of the Geography and places good articles under the good article criteria. If you can improve it further, please do so. If it no longer meets these criteria, you can reassess it. | |||||||||||||
| |||||||||||||
| Current status: Good article | |||||||||||||
| This It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||
This removed text, from the ext links,
is either incoherant or just wrong. The tracks are laid on the ground at the summit, at the crossing with the Gulfside Trail, and apparently all the way between those two points; also at the Base Station and presumably large stretches between there and Gulfside. --Jerzy(t) 19:36, 2005 Jan 18 (UTC)
Modified avalanche text
This number is more than all of the recorded deaths from all causes in all of the Presidentials, including falls, heart attacks, plane crashes, and railroad accidents. There were 2 Tucks avalanche deaths in 1954, 1 in 1956, and 2 in 2002, for a total of 5 , unless you add the one in 1996 on Lion's Head (which of course is 5 too many). Ref Howe, Nicholas(2000). Not Without Peril pp.299-304. and 11/29/2002 news at timefortuckerman.com. If we really need a fatality number, maybe it should cover all of Mt Washington, but maybe an external link to a compendium is sufficient. (updated talk) Lupinelawyer 01:45, 20 Jan 2005 (UTC)
| This help request has been answered. If you need more help, you can , contact the responding user(s) directly on their user talk page, or consider visiting the Teahouse. |
The infobox shows an error, regarding language: Native name Error: Error {{native name}}: an IETF language tag as parameter {{{1}}} is required (help): an IETF language tag as parameter {{{1}}} is required (help). The aboriginal language spoken was Western Abenaki, ISO 639-3 code: "abe". Anything that can be done to undo the error would be welcome!
HopsonRoad (talk) 18:53, 3 January 2022 (UTC)
| native_name = Agiocochook | native_name_lang = abe
|native_name_lang=, despite what the {{infobox mountain}} documentation says, is not constrained to accept only ISO 639-2 language codes. It is not clear to me why the documentation specifies ISO 639-2.|native_name= and |native_name_lang=. Questions about that should be asked there.The key col ridgeline prominence goes all the way to the Champlain Canal on the New York border over 100 miles away. The real prominence is more like 5,200 ft from the circa 1,000 ft elevation valley on the west side. B137 (talk) 08:38, 2 April 2023 (UTC)
It has been a while since this article has been reviewed, so I took a look and noticed lots of uncited statements, including entire paragraphs, especially in the second half of the article. Should this article go to WP:GAR? Z1720 (talk) 03:47, 20 July 2025 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Uncited statements, including entire paragraphs (especially in the second half of the article). Z1720 (talk) 03:05, 16 December 2025 (UTC)
It may seem obvious, but if this article is meant to stand as a general reference, a line somewhere indicating that the mountain is named after the first President of the United States would be a good idea. ~2026-10369-57 (talk) 22:22, 19 February 2026 (UTC)
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.