elihoole/asrs-aviation-reports huggingface dataset:
Date: 201702
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Flap Fairing
Reporter organization: Contracted Service
Reporter function: Trainee
Human factors: Situational Awareness
Anomaly: Ground Event / Encounter Vehicle
Detector: Person Maintenance
When detected: Routine Inspection
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: I was pulling up to the aircraft along the trailing edge of the right wing. Flaps were down to 45 position and all external lights on. As I began driving behind wing I was blinded by the right wing inspection light also the ramp overhead light disrupted my vision. The top corner of the mule vehicle contacted the tip of the flap fairing; damaging the fairing.Preventative measure is be aware of lighting conditions around aircraft. Also aircraft configuration as you drive near the aircraft.




Synopsis: An Aircraft Maintenance Technician (AMT) Apprentice reported that when driving a vehicle around a Boeing 737; the vehicle made contact with the flap fairing.
Date: 201307
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: Champion Citabria Undifferentiated
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Taxi
Aircraft component: Fuel Selector
Component problem: Improperly Operated; Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Human-Machine Interface; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Loss Of Aircraft Control; Ground Event / Encounter Object
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Sequence of events: Aircraft was out of service for extended time waiting for parts in annual inspection. Pilot arrived at airport in order to take possession of aircraft. Engine started normally; and then began to stumble. Pilot manipulated mixture and throttle in attempt to correct; without success. Pilot cycled fuel cutoff with no immediate effect. Pilot returned to manipulation of mixture; when engine power increased dramatically; overpowering brakes and taxiing aircraft into hangar door. Pilot's interpretation: The aircraft is 1946 Aeronca Champ with fuel shutoff located low on left side of cockpit. Substantial play in the handle makes it difficult or impossible to visually determine whether it is on or off. Consequently; pilot never activates fuel shutoff in normal operation. Conversation with Mechanic after event suggests that fuel shutoff may have been activated after annual inspection unbeknownst to pilot. Pilot's current opinion is that fuel shutoff led to engine stumble. Cycling the fuel cutoff led to delayed engine surge not controlled by mixture full lean setting applied. Brakes were insufficient to stop aircraft before contact with hangar door. Position of throttle during event is unknown; although the behavior of the engine suggests other than an idle setting. Corrective actions: Routine cycling of fuel cutoff before start.




Synopsis: Champ pilot experiences a rough running engine after an extended down time waiting for parts. The fuel selector; throttle and mixture are all manipulated without immediate effect. Suddenly engine power increases dramatically and the aircraft cannot be controlled before contact with the hangar door occurs.
Date: 201704
Location: ZZZ.Airport, US
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant; Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Company Policy; Procedure
Primary problem: Procedure

Narrative: We had two jump seaters; one of which was a Flight Attendant. The other jump seater was her friend [and] was NOT a crew member. She didn't work for any airline and was simply just a standby passenger. We did not find out about this until right before takeoff. The Number One FA (Flight Attendant) was looking at the Passenger list to see what airline the jump seater in the back worked for. We thought it was odd that it was not listed. This is when her friend told us that [she] was not a Flight Attendant. We were shocked that the agent let her on. We should have contacted the Captain immediately; yet we did not. I followed the lead of the Number One FA and we took off.The gate agent issued a standby passenger a jump seat. I cannot provide a reason as to why this happened. I know this is a serious and very important safety issue/violation. If I had the chance to do this over again; I would've spoken up immediately and insisted we call the Captain.




Synopsis: An air carrier Flight Attendant reported that a Gate Agent knowingly issued a jump seat to a non-crew; standby passenger who was accompanied by a jump seating Flight Attendant.
Date: 202009
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
ATC / advisory: Center ZZZ
Aircraft component: Rudder
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Took place from ZZZ-ZZZ1. In cruise at FL200 doing 300 KIAS with autopilot engaged; we experienced un-commanded yawing motions while in a right bank. We felt the rudder kick hard to the left 4 or 5 times. Both pilots feet were on the floor. When we looked at the flight controls synoptic page it confirmed the rudder was moving and strangely the rudder limiter on the left side was bouncing back and forth even though we were at a constant airspeed. After the wings rolled level the rudder stopped kicking. This was the only time the event occurred on this leg. I am not sure why the event occurred; a malfunction of some sort.




Synopsis: CRJ-900 Captain reported a temporary 'un-commanded yawing motion' during a right turn which dissipated and did not reoccur for the remainder of flight.
Date: 201212
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were on climbout and at approximately 4;000 feet. We experienced an oscillation in the #1 engine.  There were indications on the N1; ITT; and N2.  After this happened three times we declared an emergency.  We ran the QRH appropriate to the situation.  All three crew members performed their jobs in a professional manner.  We landed with no further incident.  I'm not sure why this even occurred.  Maintenance was in the process of trouble shooting when we left the aircraft.




Synopsis: CRJ200 First Officer reports engine surging climbing through 4;000 feet; which continues off and on until the crew elects to return and declares an emergency.
Date: 201908
Local time of day: 0601-1200
Location: ORD.Airport, IL
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Confusion; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: [Procedures Manual] requires B737 fan blade removal and installation qualification prior to performing the work; but [Company Learning Program] does not show the required training course as existing. B737 fan blade removal and installation. Initial qualification. Core qualified. CFM56-7B fan blade removal and installation. Reviewing [Procedures Manual] training requirement is in 19.03 but [Company Learning Program] shows the training course does not exist; but is required to be able to perform the work. This is a compliance catch-22.




Synopsis: Maintenance Technician reported that a course required for qualification to perform a specific task does not exist.
Date: 202109
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Flight conditions: VMC
Aircraft: Beechjet 400
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic System
Component problem: Malfunctioning
Reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: Other Descent
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: As we started descending into ZZZ we noticed the hydraulic gauge went up past red line (High hydraulic pressure). Pulled out the checklist and as per the checks performed a hydraulic system relief which had us do an manual gear extension; no flap landing and power brake failure landing. Went to a hold at ZZZZZ intersection to finish our manual gear extension checklist and then continued to ZZZ for a no flap ILS  to XXR and landed without incident.Hydraulic over pressure. Cause unknown.




Synopsis: Flight crew flying BE-400 aircraft reported hydraulic malfunction on descent. Landed at destination without incident.
Date: 201509
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class E ZZZ; Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Flight Instructor; Flight Crew Instrument
Human factors: Distraction
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Flying a turbine powered [single engine experimental aircraft]; climbing through about 10;000 [FT] experience a very loud BANG; aircraft pitched down; all engine indications wound down. No RPM or EGT indicated. In the turn back to the airport attempted relight. Turned on igniters; and started and still got no rotation. On departure ASOS reported winds of 12 gusting to 20 but only chance to make it back to the airport was land downwind. Extremely high density altitude and touchdown speed due to tailwinds and aircraft weight; but made it. Came to a stop about 400 feet from the end of the runway. After breathing a sigh of relief I noticed some smoke coming from behind. Egressed to find the left brake on fire. Had no fire extinguisher in the aircraft and no one responding quickly. By the time help arrived left gear was totally engulfed in flames. Fire was put out and aircraft removed from runway.




Synopsis: The pilot of a single engine turbine powered experimental aircraft experienced an engine failure. Following a successful return to the field; the left brake was found to be on fire.
Date: 202011
Local time of day: 0601-1200
Location: ZZZ.Airport, US
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: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Passenger Misconduct
Detector: Person Passenger
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: During deplaning passenger sitting in [seat] X1 complained that the passenger in [seat] Y5 had not been wearing [a] mask; which I did not observe during my walk through.




Synopsis: Flight Attendant reported a passenger stated that another passenger had not been wearing a mask.
Date: 202110
Local time of day: 1801-2400
Location: SCT.TRACON, CA
Weather elements / visibility: Low clouds obscure mtn.
Light: Night
Aircraft: No Aircraft
Operator: Other unknown
Operating under: Other unknown
Mission: Other unknown
Reporter organization: Other unknown
Reporter function: Other / Unknown; Other / Unknown
Human factors: Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Equipment Issue; No Specific Anomaly Occurred Unwanted Situation
Detector: Person Other Person
When detected: Other unknown
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Please repair the flashing FAA beacon on the peak of Mount San Miguel. A non-flashing orange light located below the highest point on the mountain has been substituting for the official FAA beacon. The current light may be emitting from one of the private television or radio antennas/antennae also on the top of the mountain. The flashing beacon is especially important when there is low visibility at night. The abrupt 2;200+ feet elevation change above sea level should have an official FAA beacon to warn the pilots. It is the tallest mountain within 15 miles of the San Diego International Airport. Please also note that this not only is a concern for aircraft; but it may also be a trespassing problem related to the ground access to the top of the mountain.




Synopsis: Observer reported Mount San Miguel possibly has a non-standard hazard light.
Date: 201301
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Aircraft component: Electrical Distribution Relay
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted
Contributing factors: Procedure; Manuals; Incorrect / Not Installed / Unavailable Part; Chart Or Publication; Human Factors; Aircraft
Primary problem: Human Factors

Narrative: I was assigned to Remove and Replace (R/R) the Generator Relay (GR) GR1 on an MD-11 aircraft. After installation of the relay; I torqued the feeder cables and connected the Generator Relay plug as per Aircraft Maintenance Manual (AMM) 24-21-05-4. I then reinstalled the access panels. I documented in Maintenance computer the removal and installation of the relay and left the item in work and turned over to next shift; as I had no more time to perform the Operational Test required per AMM. The item had been closed by the Aircraft Maintenance Technician (AMT) who performed a successful run-up and test required by the AMM; and released the Aircraft. The aircraft flew 16-legs until five days later [on the way] to ZZZ1 where it stayed on 4-day layover. At that time; ZZZ1 updated the MD-11 Information System (MDIS) as the Relay; Generator and Auxiliary Power adjustment and test was performed per AMM 24-21-05-5; using the test box. This procedure requires disconnecting the GR plugs. Later that day; the aircraft departed ZZZ1 and flew 7-legs and a diversion to ZZZ2. [Recommend that work be] checked by a second AMT.




Synopsis: A Line Mechanic reports he Removed and Replaced (R/R) a Generator Relay (GR); GR1 position; on an MD-11 aircraft. The Relay; Generator and Auxiliary Power Adjustment and Test were performed days later; but the aircraft diverted several flights after being release from Maintenance.
Date: 201907
Location: ZZZ.ARTCC, US
Flight conditions: IMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Human Factors; Procedure; Weather
Primary problem: Procedure

Narrative: While deviating for weather; the Controller instructed us to immediately turn into weather. The Captain attempted to avoid the weather; but conditions deteriorated; resulting in moderate turbulence; multiple lightning strikes upon the aircraft; and hail. The altitude deviated slightly due to weather initially; however; descent was made subsequently to 14;000 feet through several cells. Clearly the Controller did not understand the severity of the weather we were deviating around. The aircraft was landed in ZZZ uneventfully without declaring an emergency; however; it was removed from service due to burn marks on the stabilizer.




Synopsis: Flight crew reported that ATC instructions vectored aircraft into extreme weather instead of avoiding it; resulting in lightning and hail damage; requiring aircraft to be removed from service after landing.
Date: 201911
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: At the above time date and location the oil pressure was observed to be slightly above the normal operating range. This was not completely unusual in extremely cold conditions and the aircraft had remained outside on the ramp at ZZZ overnight in -13c temps and was extremely cold soaked. Within a few minutes it returned to the normal operating range; but very slowly was continuing to decrease. The pressure dropped below normal operating range Station Operations was contacted and relayed a message to and from Maintenance. They suggested we just follow flight manual guidance. The pressure slowly continued to drop. Oil temp and cylinder head temps were all normal. The Quick Reference Handbook was reviewed. As we were considering a precautionary shut down the engine failed. The QRF immediate action items were performed followed by the QRF checklist. [ATC was advised]. We were very near the top of descent for landing at ZZZ1 and the safest course of action was to continue as planned. I took over the flying pilot duties and made a normal visual approach and landing. We requested a stop on the runway and were towed off the runway to the hangar.




Synopsis: C402 Captain reported a loss of oil pressure that resulted in an engine shutdown and diversion.
Date: 201412
Local time of day: 1201-1800
Location: FRG.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class D FRG
ATC / advisory: Tower FRG
Second aircraft: Helicopter
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness; Confusion; Communication Breakdown; Time Pressure
Anomaly: ATC Issue All Types; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew Took Evasive Action
Contributing factors: Procedure
Primary problem: Procedure

Narrative: I was in the takeoff phase of a series of touch & go landings on rwy 32 at FRG. The tower had cleared a helicopter to cross 32 stating that 'he (me) would be gone before they got there'. Upon pitching to take off attitude; the helicopter was slightly to my right (moving right to left) and directly in my windscreen at climb pitch attitude. They were perhaps 300-400 feet away and it looked like I would intersect with them. I pitched down slightly and continued at about 100 feet AGL until past (under) the helicopter; at which time I pitched back to normal takeoff attitude and continued with my practice.I don't know how close I actually was; but it seemed closer than I was comfortable with.




Synopsis: A pilot on a FRG Runway 32 takeoff took evasive action during a near miss with a helicopter which should have been clear before the conflict developed.