NYC82FGT14 · Christian EAGLE II
Christian EAGLE II · Accident: on ground/water collision with object while taxiing
From Lancaster, PA to Lancaster, PA
Event
- NTSB case
- NYC82FGT14
- 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
Christian EAGLE II
- Aircraft type
- Christian EAGLE
- 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
- N3DY
- Operator
- Richard D. Yeargley · private individual
- Onboard fatalities
- Unknown
- Route
- From Lancaster, PATo Lancaster, PA
- 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
- Taxi · from runway
- 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
- On ground/water collision with object
- 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 › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TAKING OFF FROM RUNWAY 31, THE PILOT PROCEEDED TO AN AREA WHERE HE PERFORMED INVERTED FLIGHT IN AN ATTEMPT TO FIND A DIME THAT MAY HAVE BEEN DROPPED IN THE COCKPIT. DURING HIS DEPARTURE AND ARRIVAL, HE AND A TOWER CONTROLLER DISCUSSED AND JOKED ABOUT LOOKING FOR THE LOST DIME. THE PILOT WAS CLEARED TO LAND ON RUNWAY 26. WHILE ROLLING OUT, THE TOWER CONTROLLER KIDDED THE PILOT BY SAYING SOMETHING TO THE EFFECT THAT THERE WAS SOMETHING SILVER SKIPPING IN FRONT OF THE PLANE, THEN COMMENTED ABOUT GOOD VISION. THE PILOT RESPONDED, AND LATER, HE REPORTED THAT HE DID NOT HEAR THE TOWER CAUTION HIM OF EQUIPMENT ON THE TAXIWAY. THE EQUIPMENT WAS ON THE EDGE OF THE TAXIWAY BETWEEN RUNWAYS 26 AND 31. WHILE TAXIING, THE PILOT'S FORWARD VISION WAS OBSTRUCTED BY THE AIRCRAFT'S NOSE WHICH REQUIRED S-TURNS FOR CLEARING. GROUND CONTROL CLEARED THE PILOT TO CROSS RUNWAY 31, BUT INSTRUCTED HIM NOT TO DELAY SINCE THERE WAS TRAFFIC. THE PILOT ELECTED TO TAXI WITHOUT S-TURNS AND THE PLANES RIGHT WING HIT THE EQUIPMENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC82FGT14
- Event ID
- 20020917X02554
- Case number
- NYC82FGT14
- 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: 3407775ead79262dfae9be29ee991a4f097d30da8d215f4a236b51e626ee3d7a; retrieved 2026-09-24T03:20:16.296Z.