elihoole/asrs-aviation-reports huggingface dataset:
Date: 201404
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Wheels/Tires/Brakes
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Confusion; Training / Qualification
Second reporter function: Technician
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection; Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors; Staffing; Manuals
Primary problem: Human Factors

Narrative: Installed brake for Number-3 wheel incorrectly. First time doing a brake; didn't know that I could switch fittings with safety wire to other end of brake. Plane did not fly. Went back out with inspector to correct the mistake. [Recommend] providing more training and make sure someone is there to help out with first time installs.


Second narrative: Removed and Replaced (R/R) # 3 Brake. Installed incorrectly; was found before takeoff. [Recommend] further detail in Aircraft Maintenance Manual (AMM) reference for Dash-8-Q200 brake installation.


Synopsis: Two Aircraft Maintenance Technicians (AMTs) report they had Removed and incorrectly Replaced (R/R) # 3 Brake Assembly on the Right Main Landing Gear (MLG) of a DHC-8-200 aircraft. Lack of training; first time experience and lack of detail in Aircraft Maintenance Manual (AMM) were noted. An Aircraft Inspector assisted with correcting brake installation prior to departure.
Date: 201709
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Windshear; 10
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Agriculture
Flight phase: Cruise
Airspace: Class G ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: I was asked if I would like to demonstrate a Thrush agricultural aircraft for potential buyers. I was given a map showing a few close together fields I could use to make spray passes. While finishing up my last pass; I failed to provide enough clearance between the aircraft and a silage wagon parked near the edge of the field. The aircraft's left landing gear; propeller; and some spray components struck the top of the wagon. I returned to ZZZ and landed safely.I attribute this incident to my own sense of invulnerability. Through that; I was careless in planning and executing a clear departure from the field environment. I had about 5 previous spray passes that were clear on the approach and departure and I allowed myself to fall into a rhythm. Unfortunately; that rhythm didn't allow for clearance of the silage wagon.I have come away from this with many thoughts and feelings. The antidote for impulsivity has rang loud and clear; 'It could happen to me.' It DID happen to me; and it could happen to me again! It can also be a lesson to plan each approach and departure from the field before entering the field and stick with the plan.




Synopsis: Agricultural aircraft pilot reported striking ground equipment during a low level spray pass that caused minor damage to the aircraft.
Date: 201705
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Climb
Airspace: Class E ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Trainee
Reporter qualification: Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While on an instrument training flight with my instructor; I was in a climbing right turn from 2500 MSL to 3000 MSL and a heading of 330 to 150. The engine RPM went from 2000 RPM to idle. I tried unsuccessfully to regain RPM. We turned towards [the departure airport] and realized we would not make it back. The result was an off field landing in a farmers field 5 miles from [the departure airport]. The landing only caused damage to the wheel pants due to the field being wet and muddy. No injuries were sustained by myself or the flight instructor.




Synopsis: The pilot of an experimental aircraft reported an engine malfunction that resulted in an off-field landing.
Date: 201909
Local time of day: 1801-2400
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Night
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: Center ZZZZ
Aircraft component: Flap Control (Trailing & Leading Edge)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Distraction; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft B737-800; Secondary Flight Control Failure: Flaps will not extend: performed flap-less landing. Flap position indicator stopped between '0' and '1' and LE (Leading Edge) Transit amber annunciator light on. Overhead LE lights show extended.Flap fail to extend from '0' setting to '1'. This happened while on intercept for the approach ILS Runway XX. Immediately asked ATC for a hold due to technical issues and needed time to work QRH checklist. ATC instructed to hold at ZZZZZ way point as published. We then worked the QRH checklist; including an attempt to extend flaps via alternate flap system. Then set new Vref; set brakes; checked runway length; briefed crew; [advised ATC]. At this point I took control of the aircraft and became Pilot Flying. Proceeded to shoot approach; landed with no further issues and taxied to parking stand. Once parked; instructed the ground crew to only chock nose wheel; due to possible hot brakes and tires. Landing weight was 60T; Vref 190 kts.; Runway required 8100 ft. (11034 ft. available from glide slope); Touchdown speed 180 kts. (Max tire speed 195kts.); Autobrake 3; Max reverse thrust.




Synopsis: B737-800 Captain reported a failure of the wing flaps to extend; resulting in a no-flap landing.
Date: 202101
Local time of day: 1201-1800
Location: LXT.Airport, MO
Weather elements / visibility: 10
Aircraft: Small Transport
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class G LXT
ATC / advisory: UNICOM LXT
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Flight Instructor
Human factors: Communication Breakdown
Anomaly: Conflict Ground Conflict; Critical; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: I had flown into LXT to drop off passengers and then to head back to home base; ZZZ. I had made calls on 122.8 Frequency announcing my intention to taxi from ramp to Runway 36. When I approached Runway 36; I broadcasted over the 122.8 Frequency that I was taking off on Runway 36 for an east departure out of the area. I looked on final and down the runway and determined that it was clear. Runway 36 has an up slope and was not able to see the end. As I accelerated down the runway I noticed a yellow light; but because of the slope I was not able to determine where it was on the airport or what it was. As I approached my rotation speed I could see that it was a vehicle (truck) on the runway moving in the same direction as me. I felt it was safer for me to takeoff and climb over the vehicle than to abort my takeoff. I did not hear any announcements from that vehicle at any time of my taxi and taking off on Runway 36. As I departed the area VFR and announced my departure to the east I made a comment that it was not a good idea for the vehicle to be on the runway when I was taking off. The response that I received from the truck was; 'This is X vehicle clear of Runway 36.' I called on the UNICOM Frequency 122.8 and asked if the person at the FBO had heard my calls to taxi and takeoff and the said they did. I really don't know what I could have differently.




Synopsis: Small Transport aircraft pilot reported a ground conflict with a vehicle during takeoff from LXT airport.
Date: 201301
Local time of day: 0601-1200
Location: DEN.Airport, CO
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E DEN
ATC / advisory: TRACON D01
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Communication Breakdown; Other / Unknown
Second reporter function: Captain
Anomaly: ATC Issue All Types; Deviation - Track / Heading All Types
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Approaching the DANDD Intersection on the PURRL ONE RNAV STAR we cleared to maintain 210 KTS. In the turn over the DANDD Intersection to RECRD the Denver Approach Controller said; 'I needed you on the previous; uh; I needed you to; uh-fly heading 310. You were given clearance to maintain present heading.' The Captain immediately informed the Controller that we had not been assigned a heading; only a speed of 210. The Controller said 'no problem' and repeated a number of times that no traffic issues had occurred and not to worry about it. In preparing for the arrival the Captain had warned me to expect a reroute to the PURRL from our originally filed JAGGR and to expect problems from the controllers with another route; a different speed; radar vectors or different altitudes. In general; just to expect that the controllers would deviate from the published RNAV procedures. The unforeseen threat was the Controller being blatantly wrong on issuing a clearance that he didn't issue.


Second narrative: I checked in with Approach Control and told him we were out of FL210 and descending via the PURRL RNAV STAR. At some later point the Controller barked at us for not being on a 310 heading. I informed him he didn't give us a heading. He put us on a 310 heading; I had to ask him what altitude he wanted. I told him to mark the tapes. The Controller admitted it was his mistake and apologized to us several times. We did NOT miss a clearance; we did not read back a clearance incorrectly.


Synopsis: An A319 flight crew believed DEN Approach Control purposely accused them of failing to comply with clearances and replied in kind.
Date: 201512
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Air Data Computer
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: About 3 hours into cruise First Officer's PFD display started to give erroneous information including groundspeed; winds; vertical speed indications and warning flags. We also noticed all three attitude indicators showed a slight left bank. There were no other warning lights until about 20 minutes later the 'Fault' light for the right Inertial Reference System (IRS) came on. As this progressed it was apparent that our navigation was beginning to degrade because ATC said we were still heading in the right direction; but slightly off course. Eventually we completely lost the First Officer's PFD attitude display and both autopilots. Given the distance to our destination; weather; night time; degraded instrumentation and no autopilots; we decided to [advise ATC] and divert to [a nearby alternate] where the weather was clear. During descent and approach it became apparent yaw damper was inoperative also. Finally during rollout the stick shaker activated.




Synopsis: B737-800 pilot reported they diverted to an alternate airport after experiencing degraded flight data information.
Date: 201912
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Marginal
Weather elements / visibility: 6
Light: Daylight
Aircraft: Cessna 425/441 Conquest I/Conquest II
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Landing
Aircraft component: Normal Brake System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control; Ground Excursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Loss of right side brakes after landing. Upon landing roll out at the end prior to the turn; the plane started to drift left on Runway XYR; as the plane slowed down and rudder authority was lessened the attempt to correct the drift required slight braking to correct. When the brake was applied there was no braking action. Throttles were in beta to slow the plane down to make the turn off at the end of the runway. The plane eventually spun 360 degrees with the left wheel going into the grass. Once stopped (Facing the correct direction) an attempt to use differential throttle an/or Beta and Propeller pitch to clear the runway the plane spun around a second time. The gust crosswind was making control without the use of the brakes difficult. Managed to move off the runway onto the taxiway; but still not clear of the hold short line; the plane proved to difficult to control on the ground in the wind without the brake functioning. Advised Tower the plane was inoperable and needed assistance. ZZZ had to open Runway XXL which was closed by NOTAM (Notice to Airmen); and close Runway XYR as I was unable to clear the runway. The controller was extremely helpful; as well as the operations personnel at the airport.Despite at least one main wheel going into the grass and the chance of contacting light fixtures; it was all avoided. No damage to the plane; Runway lights; or injury.




Synopsis: C425 pilot reported a brake failure on landing that resulted in a runway excursion.
Date: 202001
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Other Post flight unload
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Upon arrival; a wheel chair was brought plane side for a passenger. It was noted that the wheelchair had an integrated lithium ion battery. No notification was given; and no paperwork was received by us. Arrival station agent believed it to be a manual wheelchair. Departure from ZZZ was time compressed due to an issue with aircraft cleaners and the resulting delay. It would seem that the paperwork was overlooked in part due to the pressures applied to the agents and ramp personnel to secure a departure ASAP.




Synopsis: B737 Captain reported; at gate block-in; a Lithium Ion battery powered wheelchair had been transported in cargo with no required Hazmat documentation provided prior to departure.
Date: 201710
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: Mixed
Light: Night
Aircraft: Airliner 99
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb; Initial Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Service/Access Door
Component problem: Failed; Improperly Operated
Reporter organization: Air Carrier
Reporter function: Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; Flight Crew Landed As Precaution
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Human Factors

Narrative: I departed [the Airport] with the crew hatch not fully secured. Prior to takeoff; the latch appeared to be over the pin; but was apparently not fully seated. Shortly after takeoff; wind noise increased. After clearing IMC; an attempt was made to secure the hatch. The handle bolted to the hatch tore free from the hatch allowing it to fly open and off of the aircraft. The timing was also unfortunately after frequency change approval; but before initial contact [with] Center.Prior to requesting clearance to return to [departure airport]; a turn to the north and leveling at a lower altitude was accomplished to remain close to the airport. There were storms in the area; but the incident occurred in VMC. ATC allowed return to [departure airport] to inspect for damage; the subsequent approach and landing was uneventful; priority handling was not requested or granted. There was no damage to the empennage; or its control surfaces.I think I should have contacted ATC to obtain clearance prior to making the deviation. Had the distraction occurred in IMC; the priority of clearance and communication would have been higher and the deviation would not have occurred.




Synopsis: Beechcraft 99 pilot reported taking off with the crew hatch not fully secured; and that the hatch subsequently departed that aircraft.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Tower, US
Flight conditions: VMC
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: First leg of trip. Captain's leg. AML (Maintenance Log) Review showed aircraft had just had an engine change. On takeoff; noticed odor/ fumes. As climbing out it became stronger. Cabin crew called to say they had odor/ fumes in the cabin. I assumed Pilot Flying duties while Captain coordinated with Cabin; OPS; and ATC. [ATC was notified of the situation]; CFR (crash; fire; rescue) notified. As flight progressed; odor/ fumes became less pronounced. Landed on XX; CFR said no heat signatures; followed us to gate. Normal deplaning. Cause: Engine change. Mechanic that met us said Maintenance was supposed to have done a high power run up- not sure if it was completed. Suggestions: Ensure aircraft is airworthy after major maintenance.




Synopsis: B737-800 First Officer reported an air return due to a fume event during initial climb.
Date: 201606
Local time of day: 0001-0600
Location: HEF.Tower, VA
Aircraft: Skyhawk 172/Cutlass 172
Flight plan: IFR
Flight phase: Climb
Airspace: Class D HEF
ATC / advisory: Tower HEF
Second aircraft: Skylane 182/RG Turbo Skylane/RG
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Conflict NMAC
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: Runway 16L and 16R were in use. I departed Aircraft X from 16L and departed Aircraft Y from 16R. Aircraft X was IFR on the Aersnal4 SID and Aircraft Y was VFR and was remaining in right closed traffic. I didn't think their flight paths would ever cross. Aircraft Y was in right closed traffic to runway 16R; which is the shorter runway. A normal rectangular pattern would have kept his turns inside of Aircraft X. Due to an increase in traffic volume in a short amount of time; I did not notice that he was flying a wider than normal pattern. When Aircraft X turned right his flight path conflicted with Aircraft Y; which was in the crosswind turn. When I noticed the conflict the aircraft were separated by 300 hundred feet. Aircraft X was no longer on my frequency. I immediately told Aircraft Y to enter the downwind; as it appeared he was still in a wide crosswind turn; to de-conflict their flight paths; however; I did not preface the call with 'Traffic Alert'.I would recommend emphasizing the importance of standard traffic pattern legs to the flight schools on the airport. If they want to fly a wider pattern than normal to please advise the controller so it can be expected.




Synopsis: HEF Tower Controller reported of a Near Mid Air Collision between two aircraft under his control. Controller issued traffic; but did not use the statement; 'Traffic Alert.' Reporter did not think aircraft would get close.