elihoole/asrs-aviation-reports huggingface dataset:
Date: 201405
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PC-12
Operator: Air Taxi
Operating under: Part 135
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Trailing Edge Flap
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After departing the pilot flying called for Flaps 0 degrees through 1;000 feet AGL.  The flaps were selected 0 and speed around 100-105 KIAS.  As the flap indicator approached 0 we received a Flap Asymmetry along with a Pusher Safe Aural Warning.  The Flap CAWS remained illuminated and the Pusher CAWS extinguished.  After running the QRH; we elected to return.  We landed with the flaps set in the affected position and executed a 0 flap landing.  We landed without further incident.




Synopsis: PC-12 Captain experiences a flap asymmetry as the flaps near the up position after takeoff. QRH procedures do not correct the problem and the flight returns to the departure airport.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Workload; Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Other / Unknown
Detector: Automation Aircraft RA; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: A Citation jet had cancelled IFR about two minutes prior to the RA. I was the relief pilot. No one in the cockpit saw the traffic which was called out by approach. The Citation pilot said he was VFR. We responded to the RA of 'level off' as the intruder passed underneath us; probably less than 500 ft. I did not see the PFD for the exact miss distance as I was looking out the FO's window and did acquire the intruder as he passed underneath us.




Synopsis: B757 First Officer reported a near miss with a Citation 525 which had just cancelled IFR. The 757 leveled in response to a TCAS RA command.
Date: 201809
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: With eight minutes to departure time; the pilot released brakes without approval. While I was removing the main gear brakes; the aircraft rolled back towards my feet as I was picking up the chocks.




Synopsis: Air carrier ramp agent reported the pilot released the brakes without approval prior to removal of the wheel chocks.
Date: 201810
Flight conditions: VMC
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Taxi
Aircraft component: Aileron
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Returned To Gate
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During our Flight Control check; the ailerons rolled 6 units to the right when the Yoke was released. Numerous attempts were made to do a successful Flight Control check; but each time the ailerons would consistently roll to the right when released. In discussing the issue with the mechanic on the headset; it was thought that perhaps the strong 30 knot quartering tailwind might be causing the problem. Therefore it was decided to [reposition] and attempt another Flight Control check once the aircraft was positioned differently in regards to the strong surface winds. With the aircraft facing different directions on both the ramp and the taxiway; multiple Flight Control Checks were attempted. Each time the ailerons would roll uncommanded to the right when the control yoke was released. In addition; the controls then became difficult to manually move back to the left. In discussing the matter with both our Dispatcher and Maintenance Control; it was decided to return to the gate.




Synopsis: B757 Captain reported the ailerons consistently rolled right after releasing the yoke during the off-gate flight control checks.
Date: 201407
Local time of day: 0601-1200
Location: FAT.Airport, CA
Light: Daylight
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C FAT
ATC / advisory: Tower FAT
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Workload; Distraction; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Conflict Airborne Conflict
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Aircraft; Procedure
Primary problem: Procedure

Narrative: ATC cleared an aircraft to fly a short approach that resulted in an aircraft that we had not called in sight crossing between us and our runway at less than 800 FT AGL. We executed a go-around. We passed directly above the aircraft while executing the go-around. I feel we would have struck the aircraft had we continued our approach. If we had not seen the aircraft early we would have been blindly descending into his flightpath (he was below us.)Tower cleared a training aircraft in front of us to land and assigned a flight path which crossed ours at the same altitude.Do not clear any aircraft between an arriving aircraft less than 3 miles from the runway to cross the final approach corridor; especially if the arriving aircraft do not have each other in sight.




Synopsis: Pilot reports of a go-around caused by FAT Tower Controller turning an aircraft in front of them while on short final.
Date: 201902
Local time of day: 0601-1200
Aircraft: DA40 Diamond Star
Operator: Personal
Operating under: Part 91
Flight phase: Parked
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Manuals
Primary problem: Manuals

Narrative: An AFM (Aircraft Flight Manual) is supposed to be the definitive document for operating an aircraft; weight and balance; etc.  The AFM's that I; and others; have received from Diamond Aircraft are stuffed with errors.  Equipment is listed as installed which is not; supplements for equipment that is installed are not included; Weight and Balance information is questionable because it's clear the manual does not accurately describe the configuration of the aircraft.These planes are sold in the U.S. and certified by Transport Canada; but Diamond Aircraft is being very; very sloppy.  We're paying for a certified aircraft; we should be getting accurate documentation upon delivery of a new airplane.




Synopsis: DA40 Pilot reported numerous errors in AFM; including references to equipment not installed.
Date: 201809
Location: ZZZZ.Airport, FO
Aircraft: B777 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: Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Flight Cancelled / Delayed
Contributing factors: Human Factors; Environment - Non Weather Related; Airport
Primary problem: Airport

Narrative: After departing the bus at ZZZZ we were immediately engaged by a Company reception team. They wanted to know if there was any changes to the fuel. I informed them I had no flight papers to refer to. They could not understand why I did not flight plan on the bus ride to the airport like everyone else. I received a package on the airplane that contained a copy of all the required flight papers. I was told that operations was not available for our use. I took the flight package and spread out the paperwork along with 3 iPads over the First Class area to begin flight planning. At this point the gate agents wanted to begin boarding. I immediately stopped the boarding process. Passengers should not have to walk around or take their seats in the middle of a flight crew attempting to flight plan. There is no room in the cockpit with 4 crewmembers and a constant barrage of other support people. [Company] has expressed that all crew members should plan together either in flight ops or a flight planning area. Not on a bus. Also we are not to split up. We should stay together and plan as a team.




Synopsis: B777 Captain reported conducting flight planning in the aircraft seating area at a foreign airport due to the Operations room being unavailable.
Date: 201711
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Airspace Structure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: The First Officer (FO) took off from ZZZ on runway heading Runway 6. After a direct clearance and another vector off the SID for traffic; we were cleared direct to ZZZ VOR with a climb to FL230. Direct ZZZ VOR was executed with abeam points; and we initiated the climb. Just prior to the ZZZZZ Intersection; abeam point and approximately FL200; we received an aural 'TRAFFIC' advisory. The FO slowed his rate of climb to 800 FPM using Vertical Speed (VS) to avoid setting off an RA since the other aircraft was above us. I noticed the aircraft was only 400 feet above us on the HSI and barely acquired the traffic visually when the TCAS commanded a 'CLIMB' RA. The FO immediately disconnected the autopilot; pushed the thrust levers up and initiated a climb maneuver following the RA command on the flight director. After a brief moment of climbing at an increased VS; the TCAS issued a 'CLEAR OF CONFLICT' advisory. Start to finish; the whole incident happened very quickly. I re-acquired the traffic passing to our left from beneath our nose at our 11 o'clock position and low. The Controller started to give us a Traffic Advisory but didn't really finish because the aircraft had already passed. I told the Controller that it had set off an RA in our aircraft. In the end; we had climbed through the other aircraft's altitude as a result of following the TCAS RA; and I believe we passed within three NM of the other aircraft. Being at night; it was more difficult to tell. There were several quick frequency changes that might have contributed on the Controllers' part. We notified Dispatch through ACARS. We continued the flight without further incident.Understand what conditions led to the RA and correct it/them. It was either a Controller error/misjudgment or a Pilot error in either/both aircraft. Additionally; it was a clearance not being given or received properly. I believe that we complied fully with ATC clearances and our TCAS/RA maneuver.




Synopsis: A B737 Captain reported  a 'CLIMB' RA despite the traffic above.
Date: 201703
Local time of day: 0601-1200
Location: FHU.Airport, AZ
Flight conditions: VMC
Weather elements / visibility: 30
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Initial Approach
Airspace: Class E FHU
ATC / advisory: CTAF FHU
Reporter organization: Personal
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Flight Instructor
Anomaly: Deviation / Discrepancy - Procedural Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Procedure
Primary problem: Ambiguous

Narrative: Checking DUATS; ASOS; ATIS there were numerous taxiway closures; but no listed runway closures. Flying in the pattern; it was obvious that there were parked vehicles on runway 26 at the approach end; but no X's or as previously stated; mention of closure. This is not the first time I have noticed this situation on weekends when the tower is closed.




Synopsis: C182 pilot reported there were no NOTAMs for runway closures at FHU; but noted vehicles parked on the end of Runway 26 upon entering the pattern. This situation had been noticed previously; on weekends; when the Tower is closed.
Date: 201604
Local time of day: 1201-1800
Location: WHP.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 50
Light: Daylight
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Taxi
ATC / advisory: Tower WHP
Aircraft component: Wingtip
Component problem: Improperly Operated
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Training / Qualification; Situational Awareness; Confusion
Anomaly: Ground Event / Encounter Object
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors; Procedure; Airport
Primary problem: Airport

Narrative: Primary student pilot taxiing the airplane; CFI supervising. Student turning into Runway 30 run-up area at WHP. As student turns the airplane into run-up area; Tower calls to reverse direction and taxi to Runway 12 as wind had shifted. Both student and CFI are distracted by radio call and student taxi's aircraft left wing too close to boundary fence and scrapes wingtip fairing and damages navigation light lens and bulb.Contributory factors were:1.) The yellow run-up boundary lines are placed approximately ten feet from boundary fence giving insufficient wingtip clearance for most general aviation aircraft; when using boundary lines for visual reference.2.) CFI unfamiliarity with non-standard Runway 30 run-up area boundary location marking.De-brief for student and CFU included:A) The priority of aviating (or taxiing) safely; following by navigation and communication; in that order.B) Being always aware to allow safe separation from other objects when taxiing.




Synopsis: A flight instructor reported that his student damaged the high wing aircraft's wingtip; navigation light and lens while maneuvering in the WHP Runway 30 runup area. Reportedly; taxi lines may be too close to the boundary fence.
Date: 201702
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Ground Personnel
Result: General Physical Injury / Incapacitation
Contributing factors: Equipment / Tooling; Company Policy; Human Factors
Primary problem: Ambiguous

Narrative: A worker nearly lost his life due to the negligence of [a contractor] using and not putting out of service a piece of ground equipment that posed a danger to everyone around it. My report is from information gathered from witnesses I personally spoke to; but the bottom line is the fact that he nearly lost his life because of the disregard of safety protocol used by most businesses. He was unhooking a cargo can to use when a [contractor] employee drove into the warehouse towing some universal dollies of freight and as he was making a turn the hitch of the tractor popped up and allowed the dollies to roll on their own; smashing into the worker and causing life threatening injuries. The worker was in the ICU for over a week. An employee who went to visit him says he is saying that he's just happy to be alive. [The contractor] does not follow safety rules. I personally have dozens of pictures and video of their safety violations to be used by my family in case I am incapacitated or killed by one of their employees under the same circumstances. This is not my first report about safety issues with [the contractor] and their disregard for safety. You would think that after this accident that there would be some changes; but none have been noticed by the safety coordinator. [Contractor] employees still speed around blind corners; use unserviceable equipment; not lock down freight on dollies; not secure dollies to one another; etc. I end this with what I have said before; [contractor] employees are going to cause some life altering injuries to someone or take someone's life. Yes the fact is that they are not [company] employees; but the company pays their salaries and should have a voice in how they conduct themselves around our employees.




Synopsis: Ramp Agent reported an injury to another Ramp Agent caused by a runaway freight dolly being towed by a contract worker. The reporter believes that the Contractor does not maintain their equipment and that their employees are negligent.
Date: 201303
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Light: Night
Aircraft: B777-200
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Microphone
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Communication Breakdown; Confusion; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Human Factors; Chart Or Publication; Incorrect / Not Installed / Unavailable Part
Primary problem: Human Factors

Narrative: I was assigned to work an Engineering Order on a B777-200 aircraft. The Job Card was mostly completed when I was asked to pick up on the work turnover that was already in progress. I started at Step 10; A;(7). When I arrived at the aircraft; the [flight crew] Oxygen (O2) stowage box was already installed with a completed Leak Check. The stowage boxes were already installed but not signed for; so I checked to make sure that all the fasteners were tight. From what I have been told all four O2 Mask microphones were not connected to the back side of the stowage box. There were several people that had been working on this Job Card over several shifts and I was tasked to complete an already started job. Turnovers from [Maintenance] crew to [Maintenance] crew need great improvement and the Avionic's Department needs more Operational Checks prior to release of the aircraft. Airworthiness Directive.




Synopsis: An Aircraft Maintenance Technician (AMT) was informed that all four flight crew Oxygen (O2) mask microphones on a B777-200 aircraft were found not connected to the back side of their stowage boxes. Lack of adequate Maintenance turnover communications between shifts and the need for more Avionics's Operational Checks prior to aircraft release were noted.
Date: 201310
Local time of day: 0601-1200
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: Rockwell North American Civil Twin Jet
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Taxi
ATC / advisory: Tower ZZZZ
Aircraft component: Hydraulic System
Component problem: Failed
Reporter organization: Corporate
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor
Human factors: Time Pressure; Training / Qualification
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Object; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; Flight Crew Took Evasive Action; General Maintenance Action
Contributing factors: Human Factors; Aircraft
Primary problem: Aircraft

Narrative: After a flight we were instructed to back taxi to general aviation ramp.  When back taxing on runway to general aviation ramp; loss of hydraulic pressure resulted in loss of braking and steering. Emergency braking was applied and felt as though emergency braking was engaging but was not in time to prevent aircraft from going into grass. When aircraft went into grass; the nose gear impacted an above ground concrete [structure] causing the nose gear to collapse.  We shut down and exited the aircraft. If I had a faster response the aircraft would have stopped on pavement. More emergency training.


Second narrative: No injuries and no passengers were aboard. We felt that we could stop the aircraft with emergency braking if we needed; but the emergency brakes were insufficient. We tried to manually boost hydraulic pressure; and we also tried the secondary hydraulic pump; but those systems also failed. Prior to the flight the aircraft had been inactive for an extended time.


Synopsis: A Saberliner 60 hydraulic system failed while back taxiing after takeoff but the emergency braking was insufficient to stop the aircraft which rolled off the runway where the nose gear collapsed damaging it but causing no injuries.