# Incident 20050116000529I: Beech B24R, Tyler, TX, January 16, 2005

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 16, 2005, 17:53 local time
- Place: Tyler, TX
- Airport: Tyler Pounds Field Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 32.3535° N, 95.4030° W: Placed by OpenAirDocs at TYLER POUNDS RGNL (TYR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.3535&lon=-95.4030&mi=10
- Aircraft: N23PD, registered now (https://openairdocs.org/aircraft/N23PD) (OpenAirDocs)
- Registry model: Beech B24R (registry code 1151253, https://openairdocs.org/model/beech-b24r) (OpenAirDocs)
- Registry engine: Lycoming I0360 series (registry code 41515, https://openairdocs.org/engine/lycoming-i0360-series) (OpenAirDocs)
- Reported make and model: BEECH B24R
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,297 total, 135 in this make and model, 2 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20050116000529I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) INSPECTORS STATEMENT: MY NAME IS ^PRIVACY DATA OM^. I AM EMPLOYED BY THE FEDERAL AVIATION ADMINISTRATION, SOUTHWEST REGION, DALLAS FLIGHT STANDARDS DISTRICT OFFICE (SW-05), DALLAS TEXAS 75235. DURING THE PERIOD OF 01/13/2005 THROUGH 01/20/2005, I WAS ASSIGNED THE RESPONSIBILITY OF ACCIDENT STANDBY INSPECTOR FOR THE DALLAS FSDO. ON SUNDAY, AT APPROXIMATELY, I RECEIVED A CALL FROM THE SOUTHWEST REGION COMM. CENTER THAT THERE WAS A GEAR FAILURE INCIDENT AT POUNDS FIELD, TYLER TEXAS. THE INCIDENT INVOLVED A BEECHCRAFT "SERRIA", MODEL NUMBER BE-23-B24R, REGISTRATION NUMBER N23PD. I WAS THEN PUT IN CONTACT WITH THE TOWER AT TYLER POUNDS FIELD, ^PRIVACY DATA OMI^ WHO STATED THAT THE AIRCRAFT HAD NOTIFIED THE TOWER ON APPROACH TO TYLER, TEXAS THAT THEY HAD AN INDICATION OF AN UNSAFE CONDITION WITH THE NOSE GEAR AND WANTED VERIFICATION AS TO IF THE NOSE GEAR APPEARED TO BE DOWN. THE TOWER PERSONNEL INFORMED THE PIC, IDENTIFIED AS ^PRIVACY DATA OMITTED^ THAT THE GEAR WAS ONLY PARTIALLY EXTENDED AND WAS STILL TURNED IN THE RETRACTED POSITION. THE AIRCRAFT WAS DISPATCHED TO A SECURE AREA WHILE ATTEMPTS WERE MADE TO EXTEND THE GEAR. ALL ATTEMPTS FAILED AND THE AIRCRAF                     T WAS BROUGHT BACK TO TYLER POUNDS FIELD AND CLEARED FOR A LANDING ON RUNWAY 31 AT 2353Z TIME. THE AIRCRAFT TOUCHED DOWN ON THE MAIN GEAR FOR INITIAL ROLLOUT. UPON SUFFICIENT LOSS OF SPEED, THE NOSE SETTLED ON THE PARTLY EXTENDED NOSE GEAR, WHICH SUBSEQUENTLY COLLAPSED. THE AIRCRAFT STOPPED ON THE RUNWAY WITH DAMAGE TO THE PROPELLER, NOSE GEAR STRUT AND SLIGHT DAMAGE TO THE LOWER ENGINE COWL. THERE WERE NO INJURIES TO THE PIC OR HIS STUDENT. I GRANTED PERMISSION TO THE TOWER TO REMOVE THE AIRCRAFT TO JOHNSON AVIATION AT TYLER POUNDS FIELD. ON 01/19/2005 ^PRIVACY DATA OMITT^ WHO IDENTIFIED HIMSELF AS THE PIC, CONTACTED ME. HE STATED THE SAME INFORMATION AS WHAT I HAD RECEIVED FROM THE TYLER POUNDS FIELD TOWER. THE PILOT ^PRIVACY DAT^ STATED THAT HE WOULD BE SUBMITTING AN NTSB FORM 8020-1/2. I THEN CONTACTED ^PRIVACY DATA OMIT^ OF JOHNSON AVIATION AND MADE ARRANGEMENTS TO LOOK AT THE AIRCRAFT ON 01/20/2005. ON 01/20/2005 I ARRIVED AT JOHNSON AVIATION AND BEGAN INVESTIGATING N23PD FOR DAMAGE. IT WAS APPARENT IMMEDIATELY THAT TUBE, BEECHCRAFT P/N 169-820022-1, WAS BROKEN AT THE FORWARD ROD END, (P/N 169-380082-1). IT WAS NOT APPARENT AS TO IF THE TUBE ASSEMBLY WAS BROKEN PRIOR TO THE INCIDENT OR UPON CONTACT WITH THE RUNWAY. IT WAS THEN DECIDED THAT WE WOULD CONDUCT A GEAR RETRACTION TEST TO SEEE IF THE PROBLEM COULD BE REPEATED. THE AIRCRAFT WAS PLACED ON AIRCRAFT JACKS AND THE LANDING GEAR RETRACTED. THE GEAR RETRACTED NORMALLY AND APPEARED TO EXTEND NORMALLY WITH NO FORWARD AIR PRESSURE PLACED ON THE NOSE GEAR ASSEMBLY. IT WAS THEN DECIDED TO TRY TO SIMULATE THE PROBLEM BY APPLYING RESISTANCE TO THE NOSE GEAR ASSEMBLY DURING THE EXTENSION PHASE. UPON APPLYING RESISTANCE BY HOLDING THE NOSE GEAR REARWARD, IT WAS FOUND THAT THE NOSE GEAR COULD BE PREVENTED FROM EXTENDING AND THE HYDRAULIC PUMP OF THE POWER PACK WOULD NOT SHUT OFF AFTER SUFFICIENT PRESSURE WAS BUILT UP AND THE MOTOR WOULD CONTINUE TO RUN. IT IS BELIEVED THAT EITHER THE HYDRAULIC ACTUATOR FOR THE NOSE GEAR OR THE POWER PACK ASSEMBLY WAS BYPASSING FLUID, WHICH WILL NOT ALLOW SUFFICIENT PRESSURE TO EXTEND THE NOSE GEAR OR SHUT OFF THE PUMP ROTOR. THE FLUID LEVEL IN THE POWERPACK WAS AT THE FULL LEVEL.

## Other reports on N23PD (5)

Matched to the same aircraft by N-number and date.

- [Incident 20060807015379I](https://openairdocs.org/incident/20060807015379I), Aug 7, 2006: Beech B24R (N23PD), Ft Worth, TX, Minor damage. (-23) The pilot was giving instruction to his 11 year old grandson. The pilot forgot to lower the landing gear and realized that the gear was not down after…
- [Incident 20050527009869I](https://openairdocs.org/incident/20050527009869I), May 27, 2005: Beech B24R (N23PD), Denton, TX, Minor damage. (-23) This aircraft was in cruise conditions conducting training on the use of the landing gear. The nose gear did not show a down and locked (safe) condition.…
- [Incident 20000204001419I](https://openairdocs.org/incident/20000204001419I), Feb 4, 2000: Beech B24R (N23PD), Kingston, OK, Minor damage. (-23) The pilot stated he extended the landing gear and had three green lights, after touch down the nose gear collapsed. Inspection of the nose gear system…
- [Incident 19911118058349I](https://openairdocs.org/incident/19911118058349I), Nov 18, 1991: Beech B24R (N23PD), Carthage, MO, Minor damage. Landing gear collapsed on landing rollout. Pilot stated he had three green lights.
- [Incident 19900718035059I](https://openairdocs.org/incident/19900718035059I), Jul 18, 1990: Beech B24R (N23PD), Fort Smith, AR, Minor damage. Nose gear collapsed on landing rollout. Found nose gear was not locked down.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
