Narrative:

Start fault was detected during #2 engine start with ECAM message 'engine #2 'a' ignition fault' 'restart' fadec automatically aborted, cleared and restarted with ECAM message 'ab' ignition engine started normal. During after start ECAM status was check with 'normal' no faults was noted! Thinking fadec saw something it didn't like then reset or fixed itself on second attempt, we continued flight to ZZZ1. I decided to talk to maintenance about start with logbook entry. It was later discovered that 'a' system engine had failed somewhere not sure. Also found out that aircraft was not to be dispatched with a system inoperative. Should have been more explicit with logbook entry.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN AIRBUS 319 WAS DISPATCHED IN NON COMPLIANCE WITH R ENG 'A' IGNITION INOP IN CONFLICT WITH THE MEL.

Narrative: START FAULT WAS DETECTED DURING #2 ENG START WITH ECAM MESSAGE 'ENG #2 'A' IGNITION FAULT' 'RESTART' FADEC AUTOMATICALLY ABORTED, CLRED AND RESTARTED WITH ECAM MESSAGE 'AB' IGNITION ENG STARTED NORMAL. DURING AFTER START ECAM STATUS WAS CHK WITH 'NORMAL' NO FAULTS WAS NOTED! THINKING FADEC SAW SOMETHING IT DIDN'T LIKE THEN RESET OR FIXED ITSELF ON SECOND ATTEMPT, WE CONTINUED FLT TO ZZZ1. I DECIDED TO TALK TO MAINT ABOUT START WITH LOGBOOK ENTRY. IT WAS LATER DISCOVERED THAT 'A' SYS ENG HAD FAILED SOMEWHERE NOT SURE. ALSO FOUND OUT THAT ACFT WAS NOT TO BE DISPATCHED WITH A SYS INOP. SHOULD HAVE BEEN MORE EXPLICIT WITH LOGBOOK ENTRY.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.