In this paper we introduce a new concept for flight-critical integrated software and hardware systems to analyze themselves forensically as needed as well as keeping forensics data for further automated analysis in cases of reports of anomalies, failures, and crashes. We insist this should be a part of the protocol for each system, (even not only flight systems), but any large and/or critical self-managed system. This proposition is a rehash of the related work of the author during his PhD studies [1, 2] for the NASA spacecraft self-forensics concept as well as a work towards improving the safety and crash investigation of read vehicles with similar means. We review some of the related work that these ideas are built upon prior describing the requirements for self-forensics components. We describe the general requirements as well as limitations and advantages. This is a draft sketch.

This paper further introduces and formalizes a novel concept of self-forensics for automotive vehicles, specified in the Forensic Lucid language. We argue that self-forensics, with the forensics taken out of the cybercrime domain, is applicable to "self-dissection" of intelligent vehicles and hardware systems for automated incident and anomaly analysis and event reconstruction by the software with or without the aid of the engineering teams in a variety of forensic scenarios. We propose a formal design, requirements, and specification of the self-forensic enabled units (similar to blackboxes) in vehicles that will help investigation of incidents and also automated reasoning and verification of theories along with the events reconstruction in a formal model. We argue such an analysis is beneficial to improve the safety of the passengers and their vehicles, like the airline industry does for planes.