NYC06CA031 · Beech F33A
Beech F33A · Accident: hard landing
From AIY · Atlantic City, NJ to Orange County Airport (MGJ)
Event
- NTSB case
- NYC06CA031
- 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
- 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 F33A
- Aircraft type
- Beechcraft 33
- 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
- N1813W
- Operator
- Shirley A. Onacilla · private individual
- Onboard fatalities
- Unknown
- Route
- From AIY · Atlantic City, NJTo Orange County Airport (MGJ), Montgomery, NY
- 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
- 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
- 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
- Pilot in command › Flare, misjudged
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was making a night visual approach to an airport when, on short final, the pilot-activated runway lights timed out. The pilot re-activated the lights, which came back on at a high intensity that "adversely affected [her] night vision and depth perception." During the time the lights were out, the airplane descended below the glide path, and by the time she realized it, the pilot felt that she could not have successfully executed a go-around because "the aircraft would have most likely lost lift and stalled." According to a Federal Aviation Administration inspector, the airplane then landed "short and hard." No airplane mechanical anomalies were noted.
Probable cause
The pilot's misjudgment of the landing flare, which resulted in a hard landing short of the runway. Factors included the night lighting conditions, the time-out and reestablishment of the high intensity runway lighting, and the pilot's failure to go around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC06CA031
- Event ID
- 20060110X00038
- Case number
- NYC06CA031
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-11-12.
- API snapshot SHA-256: ac980150c125985e5503bf271b9c99c4fda3d57a06de7c2ebf786b6faf31dc2a; retrieved 2026-09-22T05:14:55.382Z.