NYC83FNC08 · Cessna 172L
Cessna 172L · Accident: hard landing
From Hancock County-Bar Harbor Airport (BHB) to an unrecorded destination
Event
- NTSB case
- NYC83FNC08
- 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
- 0
- 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
- General aviation
- 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
Cessna 172L
- Aircraft type
- Cessna 172
- 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
- N3821Q
- Operator
- Stephen Elgin Sallee
- Onboard fatalities
- Unknown
- Route
- From Hancock County-Bar Harbor Airport (BHB), Bar Harbor, METo not recorded
- Aircraft age
- Not recorded
- 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 91: General Aviation
- 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
- First occurrenceThe 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Compensation for wind conditions, improper
- Pilot in command › Go-around, delayed
- Pilot in command › Recovery from bounced landing, improper
Approximate · Estimated position: the centre of Moose River, ME, the place the record names. Not the accident site.
NTSB narrative
THE PLT REPORTED THAT HE ENCOUNTERED WIND SHEAR & STALLED ON FINAL APPROACH, WHICH RESULTED IN A BOUNCED LANDING, THEN THE PLANE SETTLED AND BOUNCED AGAIN. HE REPORTED THAT HE ATTEMPTED TO GO AROUND, BUT COULD NOT GET THE ACFT TO ACCELERATE TO CLIMB SPEED. DURING THE ATTEMPTED GO-AROUND, THE ACFT STRUCK TREES & CRASHED. THE PLT ESTIMATED THE WIND WAS FROM 270 DEG AT 20, GUSTING 30 KTS. THE INVESTIGATING INSPECTOR LANDED IN A CESSNA 172, APRX 1 HR AFTER THE ACCIDENT. HE NOTED THAT THE WIND CONDITIONS WERE THE SAME AS WHAT WAS REPORTED BY THE PLT, EXCEPT THE INSPECTOR DID NOT ENCOUNTER WIND SHEAR.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FNC08
- Event ID
- 20001214X43908
- Case number
- NYC83FNC08
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: f2894d0249bd70b9644c64f6381bf3fd6d53fed4a62c9a5dccf84db83ccbc77f; retrieved 2026-09-22T02:35:13.995Z.