EMB-145 Technician reported an aircraft had a rejected take off due to no airspeed indications. An inspection of the aircraft revealed an RII block was checked wrong; resulting in an inspection not being done.

Date: 2022-04 · Aircraft: EMB ERJ 145 ER/LR · Phase: ground

Anomalies: aircraft-equipment-problem-critical|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-maintenance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-clearance

Synopsis

EMB-145 Technician reported an aircraft had a rejected take off due to no airspeed indications. An inspection of the aircraft revealed an RII block was checked wrong; resulting in an inspection not being done.

Narrative

On Date Aircraft X had an open write up for an ADC issue. The PM shift began troubleshooting the problem with Maintenance and performed a task a certain way thinking that it wouldn't be RII since they were not opening both systems at the same time per the RII list. With contract having no success after the re-rack one side at a time which wasn't documented in the logbook and only listed in a turnover; the RII was missed. A ZZZ road trip was set up prior to my arrival with limited parts and tooling. The mechanics that were sent already had an idea of what needed accomplished and had the required references needed in the event; so when they arrived at the aircraft they went to work immediately.The mechanics had a few issues during ops and leak checks and reached out to another base for some direction per my request. Shortly after; the checks began going smoothly and knowing the checks a quite lengthy I let them work with little to no interruptions only for a fatigue check. Around XA:00 they stated that the write up should be signed off within the hour pending the results of the final function check that was required; then would have to remove all the test equipment and complete the paperwork; while requesting to be put on the first flight out back to ZZZ which was the aircraft they were fixing. I had asked that a member of morning shift get that process started since I was going to be off shift when they were supposed to depart. As XB:00 approached; operations and dispatch were asking for a RTS update along with a rush to try and get the mechanics checked in on the flight since it an hour prior cut off; all while not knowing where the mechanics stood close out and clean up wise. At XB:15 the mechanics finally uploaded a photo of the completed logbook; while I was in the middle of typing my turnover to the morning shift for them to take over; with the flight due out shortly I checked the verbiage they entered and verified the references they listed then began entering all the information in to the maintenance systems trying to keep the flight on time looking over the 'no' circled under RII when in fact it is RII. The aircraft was released for flight but aborted takeoff due to not having any air speed indication even though the air speed checked fine during the function check. The aircraft RTG and another road trip was set up after I had gone home for the day.Always document all work completed on the aircraft and verify the work done is cross checked with the RII list. Also don't rush paperwork to try and save the right start. Not creating a discrepancy for troubleshooting causing a missed RII with contract maintenance and rushing over paperwork at shift end to not cause a maintenance delay.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.