Atlas Air Flight 8601
Boeing 767 38E · Accident: hard landing
From Frankfurt-Hahn Airport (EDFH) to Portsmouth International Airport at Pease (PSM)
Event
- NTSB case
- DCA18CA252
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Boeing 767 38E
- Aircraft type
- Boeing 767
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N641GT
- Operator
- Atlas Air
- Onboard fatalities
- Unknown
- Route
- From Frankfurt-Hahn Airport (EDFH), HahnTo Portsmouth International Airport at Pease (PSM), Portsmouth, NH
- Aircraft age
- About 26 years (built 1992)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On July 27, 2018, about 0452 eastern daylight time, Atlas Air Incorporated flight 8601, a Boeing 767, N641GT, experienced a hard landing at Portsmouth International Airport at Pease, (KPSM), Portsmouth, New Hampshire. There were no injuries to the 250 passengers and crew onboard. The airplane was substantially damaged. The non-scheduled supplemental international passenger flight was operated under the provisions of 14 Code of Federal Regulations Part 121 from Frankfurt-Hahn Airport (HHN), Hahn, Germany, to KPSM.
The captain, a line check-airman, was the pilot monitoring and the first officer was the pilot flying and was completing his first operational evaluation. The takeoff, cruise and descent were normal. Visual meteorological conditions with light winds prevailed at the time of the landing. As the FO initiated the landing flare, the airplane became slightly high on the approach path (1 red and 3 white on the Precision Approach Path Indicators). According to the operator, the airplane touched down with limited flare and the engines were at nearly 50% N1, which inhibited the speedbrakes from deploying. The Quick Access Recorder (QAR) data indicated that the airplane porpoised five times down the runway. The maximum load factor recorded during landing bounces was about 2 g’s. Post landing inspection of the airplane found visibly wrinkled, dented and creased skin in the forward fuselage upper crown area, deformation to the nose wheel-well side web, and buckling/fracture of multiple frames and stringers.
Probable cause
an improper landing flare technique and the lack of the appropriate bounced landing recovery procedure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA18CA252
- Event ID
- 20180727X04921
- Case number
- DCA18CA252
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 10d5c2d4c3cd0aef4d0e54bde775f7142ddc5f188e96ee615e1dd65e33be08ee; retrieved 2026-09-16T08:00:29.331Z.