NYC84FA165 · Beech B19
Beech B19 · Accident: loss of control in flight during initial climb
From College Park Airport (CGS) to Cambridge Dorchester Airport (CGE)
Event
- NTSB case
- NYC84FA165
- 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
Beech B19
- Aircraft type
- Beechcraft 19
- 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
- N18786
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From College Park Airport (CGS), College Park, MDTo Cambridge Dorchester Airport (CGE), Cambridge, MD
- 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
- Initial climb
- 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
- Loss of control in flight
- 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
- Aircraft performance, climb capability › Deteriorated
- Pilot in command › Proper climb rate, not attained
- Pilot in command › Wind information, inattentive
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLT HAD ARRIVED AT THE ARPT BETWEEN 1600 & 1615, & HAD LANDED ON RWY 15. WINDS GENERALLY WERE OUT OF THE SW AT ABOUT10 KTS. THE PLT STATED THAT DURING THE FLT HE HAD OBSERVED A THUNDERSTORM WEST OF ANDREWS AFB (10 MI SOUTH.) AFTER LOADING AN ATC SIMULATOR & ITS ACCESSORIES ON BOARD THE ACFT, THE PLT TAXIED TO THE DISPLACED THRESHOLD ON THE APPROACH END OF RWY 15. DURING THIS PERIOD, ANEMOGRAM READINGS RECORDED BY THE UNIV OF MD SHOW THAT THERE WAS A SUDDEN SHIFT TO WINDS OUT OF THE NW WITH GUSTS TO 40 KTS. THE PLT COMMENTED THAT HE WANTED TO BEAT THE STORM. WITNESSES REPORTED THAT THE WIND WAS BETWEEN 300 & 330 DEGS WITH WINDS IN EXCESS OF 20 KTS. ONE PLT TRIED TO WARN THE PLT BY WAVING HIS ARMS TO CALL HIS ATTENTION TO THE WIND CONDITIONS. THE ACFT TOOK OFF IN A NOSE HIGH ATTITUDE. THE PLT STATED HE MAINTAINED 75 KTS AT MAX POWER BUT THE ACFT CONTINUED TO DESCEND AT ABOUT A 200 FPM DESCENT UNTIL IT IMPACTED TREES & FENCES OF A TENNIS COURT. A 24 KT TAILWIND COMPONENT CAN INCREASE TAKEOFF DISTANCES BY AS MUCH AS 80%.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC84FA165
- Event ID
- 20001214X39711
- Case number
- NYC84FA165
- 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: c615b899be789222ef91a9efc0c809ed8f5041e2960d755129d327ba163213e8; retrieved 2026-09-21T17:37:19.988Z.